Contents x
    Groups
    • 19 Nov 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Groups

    • Updated on 19 Nov 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Groups listed here are from identity sources added to your Liquit System.

    Currently it is not possible to add, remove or edit any groups. However, it is possible to assign packages and access policies to the existing ones.

    To view the details of a group, double-click its entry.

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

    Overview screen

    In this screen you can view the name, display name and description of the group.

    Members screen

    In this screen you can view the users that are members of the current group.

    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.

    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