Antylogic
DemoApp login

399 operational guides

Docs sections
DocsAccess
Device

Create an organisation role

Create a role owned by Harbor Demo Group, choose whether it applies to organisation or location-level work, select the initial permissions, and return to the Roles tab. This creates the role only; assigning it to users is a separate action.

In this article

Organisation roles let access administrators define what a future group of users may do before those users are assigned. In Harbor Demo Group, the role is created from the organisation access area and can use either Organization scope or Location scope.

The save is a two-part flow: Antylogic creates the role first, then saves the selected permission assignments. The documentation should not describe the action as atomic, and it should not imply that any user receives the role during this flow.

Before you start

  • You are signed in to Harbor Demo Group with Harbor Soho selected in the GB demo runtime.
  • Your account can view the access area and manage roles and permissions for the organisation.
  • The organisation permissions catalogue is available.
  • Use a role name that does not already exist in Harbor Demo Group.

Instructions

  1. 1.

    Open the Roles tab

    Open `organization/access?tab=roles`. The Roles tab shows current roles, the scope filter, the Owner column, and the Create role action when your account can manage permissions.

  2. 2.

    Start the new role

    Select Create role to open `organization/access/roles/create?tab=roles`. The form starts with an empty role name, optional description, Organization scope selected, and a permissions table filtered to that scope.

  3. 3.

    Enter role details

    Enter a unique role name and, if useful, a description. Keep Organization scope for organisation-level permissions, or switch to Location scope for a role owned by the organisation but usable with location-level permissions.

  4. 4.

    Select initial permissions

    Select at least one permission from the table. Search can narrow the list by permission code or description, and changing scope removes selected permissions that no longer match the new scope.

  5. 5.

    Create the role

    Select Create role. Antylogic creates the role, saves the selected permission assignments, shows the Role created confirmation, and returns to the Roles tab.

  6. 6.

    Cancel if needed

    Use Cancel or Back to roles to return to the Roles tab without creating a role or changing permission assignments.

Validations and limits

  • Create role stays disabled until the role name is not blank after trimming and at least one permission is selected.
  • Duplicate role names are rejected by persistence rules; the screen does not pre-check duplicates before submit.
  • Only Organization and Location scopes are available in this organisation flow. System roles cannot be created here.
  • Organization scope accepts organisation permissions, Location scope accepts location permissions, and system permissions are excluded.
  • There is no location picker on this screen; a Location-scope role created here is still owned by the organisation.
  • Operators with view access but without manage access can review the form in read-only mode, without selectable permissions or Create role.
  • The role save and permission assignment are separate operations. If permission saving fails after the role is created, the interface reports the error but does not roll back the created role.
  • Creating the role does not assign it to users.

Expected result

The new organisation-owned role appears in the Roles tab with its initial permission assignments. Users are assigned to that role in a separate workflow.

Related articles