Users
  • 14 Feb 2023
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Users

  • Dark
    Light
  • PDF

Article Summary

Users listed here are from Identity Sources and from the LOCAL identity source added to your workspace environment.

Currently you can only add or remove users within the LOCAL identity source.

To view the details of a user or edit it, double-click its entry.

See below the description of each screen in the detailed view of a user, and what actions you can perform in each of them.

Overview screen

The Display name, Email and Password can be edited only for local users.

Memberships screen

Displays a list of all the groups that the current user is a member of.

To view the details of a group or edit its packages and access policies, double-click its entry.

Access Policies screen

Access Policies allow you to grant or restrict access to certain components in the Liquit Workspace.

For a more dynamic customization, access policies can be defined on different levels; while the inheritance flows top-down, a local override has priority. This means an access policy assigned at the group level can be overridden by an access policy defined at the user level.

Events screen

Displays all events that are associated with the current user.

Logged on screen

Displays a list of devices currently hosted or logged on.

Packages screen

View a list of all packages currently assigned, assign new or remove existing ones.
To view the details of a package or edit it, double click its entry.
To add a package, simply start typing in the lookup field for the desired package and select it from the results lists. Or select the browse button browse-icon-1x.png at the right of the lookup field to open the Package dialog box to view all the packages available. When assigning the package, you will be prompted to choose between different stages that should be published to the user (Development, Test, Acceptance or Production).
Note that you can override an entitlement for a package, via Context, Device collections, Groups, or user-level and the lowest stage will take priority. The lowest stage is Development and the highest stage is Production.


Scenario:

  • User1 is directly entitled for PackageA in Production stage.
  • User1 is also part of a device collection that has PackageA assigned with Test stage.

In this scenario, the Test stage version of the package will be deployed to the user, as it is of a lower priority.


Tip

To see all the entitlements for a package, go to Manage > Workspace > Packages > Entitlements

For more information about publishing options and events, see Packages.


Was this article helpful?

What's Next