Antylogic
DemoApp login

399 operational guides

Docs sections
DocsAccess roles and permissions
Device

Assign a Role to a User

Give an existing user an existing access role at organisation or location level. Select the role in the user detail view, then save the change; ticking a role is only a pending selection until Save changes is pressed.

In this article

Use this guide when a Harbor Demo Group administrator or Harbor Soho manager needs to grant an existing access role to an existing user. The role must already exist and its permissions are not edited during this action.

The same workflow exists at organisation and location level. Location assignments are scoped to the selected location, while organisation assignments are stored at organisation level.

Before you start

  • The operator is signed in with an active organisation. Location-level assignment also requires the selected Harbor Soho location context.
  • The target user already exists, is visible in the current Users tab, and has accepted membership in the relevant organisation or location.
  • The target role already exists in the applicable role list and is not the synthetic owner role.
  • The operator can review users and roles with view permissions, but needs permissions:manage to change assignments.

Instructions

  1. 1.

    Open the Users tab

    Open the Users tab in organisation access for Harbor Demo Group, or in location access for Harbor Soho when assigning a location role.

  2. 2.

    Select the user

    Open the user detail page. The page loads the user, the available roles, and the roles already assigned in the current context.

  3. 3.

    Review existing roles

    In the Roles section, check the current selections before changing anything. Operators without permissions:manage see this section in read-only mode, and the owner pseudo-role cannot be assigned manually.

  4. 4.

    Select the new role

    Tick the role to add. This changes the on-screen selection only; the app does not send the assignment request until Save changes is pressed.

  5. 5.

    Save the changes

    Press Save changes. The app assigns each newly selected role, refreshes user and permission data, shows the success state, and returns to the previous screen.

  6. 6.

    Alternative: create an internal location user with roles

    From location access, create an internal user and select location roles in the same form. The user is created first, then each selected role is assigned. This variant is not valid for organisation-level internal user creation.

Validations and limits

  • Organisation assignment uses POST /api/app/{orgId}/users/{userId}/roles/{roleId} with body {}.
  • Location assignment uses POST /api/app/{orgId}/{locationId}/users/{userId}/roles/{roleId} with body {}.
  • The role ID is read from the route path, not from a role_id field in the request body.
  • The UI sends one request per newly selected role; there is no bulk assignment endpoint.
  • Assigning an existing user-role relationship is treated as a successful no-op.
  • The owner pseudo-role is synthetic, disabled in the UI, and is not a normal user_roles record.

Expected result

The user has the selected existing role in the chosen organisation or location context, and the app refreshes cached user and permission data so effective access is up to date.

Related articles