See the complete route index at https://docs.crusible.dev/llms.txt before following links.

# Remove a member

Remove a colleague’s workspace access and understand what remains.

<!-- https://docs.crusible.dev/admin/remove-a-member/ · doctype: how-to · role: admin · reviewed: pending human review -->


You need permission to remove members. This menu only removes other members.
Removal keeps the account; the person’s data remains.


1. <p>Open <strong>Directory</strong> at <code>/organisation/directory</code> and find the member. Confirm their identity before continuing.</p>
 (Result: Directory shows the person whose access you intend to remove.)

1. <p>Open the member’s action menu and select <strong>Remove user</strong>.</p>
 (Result: A confirmation explains the access change and retained account.)

1. <p>Read the confirmation and select <strong>Remove</strong>. Complete an identity check if requested.
Check the result before assuming the person has lost access.</p>
 (Result: Crusible removes access after accepting the request.)

- **If this doesn't work:** <p>Select <strong>Cancel</strong> to leave access unchanged.
If removal fails, read the displayed reason. Crusible protects the last owner and checks your permission again.
An absent action can mean that you lack permission or that the target is your own account, an agent or an unsupported account state.
Ask an organisation owner to check the member when the reason remains unclear.</p>





The account remains available for a permitted administrator to restore with **Restore access** when the menu offers that action.
For an open invitation, use **Revoke** instead.

- [Invite people and set roles](https://docs.crusible.dev/admin/invite-and-set-roles/) — Invite colleagues from Directory and change an active member’s access from their profile.- [Roles and permissions](https://docs.crusible.dev/admin/roles-and-permissions/) — Organisation roles, settings access and the limits on changing another member’s access.