Antylogic
DemoApp login

399 operational guides

Docs sections
DocsAccess control
Device

Delete Access Role

Remove one editable access role owned by the current organisation or location scope. Standard, system, inherited and read-only roles stay visible for context but cannot be removed from this action.

In this article

Use this guide when a temporary or discardable access role must be removed from Harbor Demo Group or from the selected Harbor Soho location. The route you use sets the boundary for the deletion.

Deleting a role removes the role itself and the linked permission and user-role assignments. It does not delete users and it does not remove entries from the permissions catalogue.

Before you start

  • The operator is signed in, Harbor Demo Group is selected, and Harbor Soho is selected for the location variant.
  • The operator has `permissions:view` or `permissions:manage` to open User roles, and `permissions:manage` to delete a role.
  • The target role is temporary or no longer needed and belongs to the current scope: organisation roles belong to the current `ORG_ID` with no `location_id`, while location roles belong to the current `LOCATION_ID`.
  • Do not delete standard catalogue roles such as Organization administrator, Location administrator, Front desk, Cashier or `owner`.

Instructions

  1. 1.

    Open the correct User roles list

    Open `organization/access?tab=roles` to manage Harbor Demo Group roles, or `location/access?tab=roles` to manage Harbor Soho roles. The User roles tab is the starting point for deleting from the list and for opening role details.

  2. 2.

    Choose an owned editable role

    Find a temporary custom role in the table. Use the Scope and Owner columns to distinguish roles owned by Harbor Demo Group or Harbor Soho from system or inherited roles.

  3. 3.

    Start deletion from the list

    Open the row menu for the editable role and choose Remove. Antylogic opens the Delete role confirmation dialog with Delete and Cancel actions.

  4. 4.

    Confirm the deletion

    Select Delete only after confirming that the role is temporary or no longer needed. On success, the app shows Role deleted and refreshes the User roles list.

  5. 5.

    Use the role detail path when needed

    As an alternate path, open `organization/access/roles/:roleId?tab=roles` or `location/access/roles/:roleId?tab=roles`. For an editable existing role, use the footer Remove action, confirm Delete role, and return to User roles after success.

  6. 6.

    Review the impact

    The delete removes the role record, its `role_permissions` links and its `user_roles` assignments. Users and the permissions catalogue remain unchanged.

Validations and limits

  • The User roles tab is available only when the operator has `permissions:view` or `permissions:manage` in that scope.
  • Deleting requires `permissions:manage` in the same organisation or location scope.
  • The organisation route deletes only organisation-owned roles; the location route deletes only roles whose `location_id` matches Harbor Soho.
  • Remove is available only for owned editable roles and remains unavailable for system, inherited, standard or read-only roles.
  • The action deletes one role at a time; there is no bulk delete path and no request body is sent.
  • The detail footer does not delete in create mode, read-only mode, without a loaded role or without a `roleId`.
  • If the API rejects the request, the UI shows Unable to delete role with the resolved error message.

Expected result

The temporary access role is removed from the current scope, the role list and detail queries are refreshed, linked permission rows and user-role assignments are cleared by cascade, and users and catalogue permissions remain intact.

Related articles