Antylogic
DemoApp login

399 operational guides

Docs sections
DocsAccess, Roles and Permissions
Device

Remove a Role from a User

Use the user detail screen to remove an existing role assignment from a user in the current organisation or location scope. The change removes only the role assignment; it does not delete the user or the role definition.

In this article

This guide covers the operator flow for removing a role assignment from a user in Harbor Demo Group or Harbor Soho. The action is completed from the user detail screen by clearing a role selection and saving the change.

Organisation and location scopes are separate. Remove organisation roles from the organisation user detail, and location roles from the location user detail.

Before you start

  • You are signed in with an organisation selected. For location-level roles, a location such as Harbor Soho is selected.
  • The target user is visible from `organization/access?tab=users` or `location/access?tab=users`.
  • The role is already assigned to that user in the same scope where you are working.
  • Your effective permissions include `permissions:manage` for the current organisation or location.
  • The role to remove is not `Owner`, because Owner is synthetic and is not removable from this screen.

Instructions

  1. 1.

    Open the users list

    Go to Access and open the Users tab for the scope you want to change. Use organisation access for organisation-wide roles, or location access for a Harbor Soho role.

  2. 2.

    Open the user detail

    Open the target user from the row action. The detail screen loads the user record, available roles, and the roles currently assigned to the user.

  3. 3.

    Review the roles table

    Find the roles section. Operators with `permissions:manage` can use the selection controls and the Save changes footer. View-only operators can inspect roles but cannot change them.

  4. 4.

    Clear the role selection

    Clear the assigned role you want to remove. Do not clear Owner: it is derived from organisation ownership and is shown as selected and disabled when applicable.

  5. 5.

    Save the change

    Select Save changes. Organisation scope sends `DELETE /api/app/{orgId}/users/{userId}/roles/{roleId}`; location scope sends `DELETE /api/app/{orgId}/{locationId}/users/{userId}/roles/{roleId}`. The request has no payload.

  6. 6.

    Confirm the result

    After a successful save, the app shows success feedback, refreshes access data, and returns to the Users list. Reopen the user detail if you need to confirm that the role is no longer selected.

Validations and limits

  • The API requires `permissions:manage` in the same organisation or location context.
  • A successful deletion returns `204 No Content`.
  • Removing a role assignment does not delete the user and does not delete the role from the role catalogue.
  • There is no dedicated Remove role button or confirmation modal for this action.
  • Multiple role changes are saved as sequential API calls: removals first, additions second.
  • The verified implementation does not show a backend rule that blocks removing a user’s last role or removing a role from the current actor beyond permissions, existence, and scope checks.

Expected result

The selected role assignment is removed from `user_roles` for the current scope, while the user record and role definition remain available.

Related articles