Antylogic
DemoApp login

399 operational guides

Docs sections
DocsAccess management
Device

Update an access role

Update the name and description of an editable access role owned by Harbor Demo Group or Harbor Soho. Permissions are visible on the same screen, but changing them belongs to access.roles.set-permissions.

In this article

Use this guide when an administrator needs to keep role labels clear without changing what the role can do. The editable fields are Name and Description; Scope stays locked for existing roles.

The same workflow exists at organisation and location level. In the location view, only roles owned by Harbor Soho are editable; inherited, global, and system roles open in read-only mode.

Before you start

  • You are signed in with Harbor Demo Group selected. For the location flow, Harbor Soho is the active location.
  • Your account can view role details and has permission management access in the relevant organisation or location scope.
  • An editable role already belongs to the active scope: Harbor Demo Group for the organisation route, or Harbor Soho for the location route.
  • The role keeps at least one permission selected before saving, because the form disables Save when no permission remains selected.
  • Do not use system, global, or inherited roles for the editable example; those are read-only in the normal UI.

Instructions

  1. 1.

    Open the User roles list

    Open Access management and switch to User roles. Use organization/access?tab=roles for Harbor Demo Group, or location/access?tab=roles for Harbor Soho.

  2. 2.

    Choose a role owned by the active scope

    Select Edit on a role owned by the current organisation or location. Rows outside that editable scope show View instead.

  3. 3.

    Change the role details

    In Role details, update Name and/or Description. Leave the permission rows unchanged when documenting this action, because permission replacement is a separate workflow.

  4. 4.

    Save the update

    Select Save once the form has a real change, a non-empty name, and at least one selected permission. Antylogic saves only the role name and description for this action.

  5. 5.

    Check the result

    Confirm that the app returns to the same User roles list with Role updated visible, and that the role remains in the same owner and scope context.

Validations and limits

  • Save is disabled until something has changed, the name is not empty after trimming, at least one permission remains selected, and no save is already running.
  • Scope is locked for an existing role; changing between Organization and Location requires creating another role.
  • If only permission rows changed, this role update endpoint is not called; that save belongs to access.roles.set-permissions.
  • System, global, inherited, or wrong-location roles are read-only from this screen.
  • If the backend rejects the update, the operator stays on the form and sees Unable to save role.
  • Existing user assignments and permission selections are not changed by this action.

Expected result

The access role keeps the same scope, owner, permissions, and user assignments, with only its name or description updated.

Related articles