Roles and permissions
Organisation roles, settings access and the limits on changing another member’s access.
Organisation roles and channel access apply at different scopes. A role controls organisation permissions. Channel settings control access to a particular channel and its work.
Organisation roles
Directory displays Owner, Admin, Member or Guest in a member’s Access field. An invitation carries the access offered to its recipient.
The member profile offers Guest, Member and Admin when you have permission to change roles. Owner is absent from the menu. Ownership transfer is a separate operation and has no role-menu shortcut. Your own role and an owner’s role remain read-only here. The control applies to active human members, not agents or inactive accounts. Crusible also checks your authority when you submit the change. Crusible can refuse a requested change even when the menu is visible.
Settings permissions
| Area | Access boundary |
|---|---|
| Personal settings | Your own profile and preferences |
| Directory | Roster access, invitations, role changes and removal each require their own permission |
| Labels | Reading the catalogue and managing labels require different permissions |
| SSO | The organisation owner manages the connection |
| Credits and billing | Requires billing permission; the page has no billing controls yet |
| Other organisation pages | Each page requires its own permission |
Settings navigation omits pages outside your permissions. A member who can read Directory might not see Invite people, a role menu or Remove user. Some sensitive changes request a fresh identity check before they proceed. Crusible refuses a change that would remove the last owner.
Access within a channel
Private channels can restrict access independently of organisation membership. Visibility, membership and posting controls apply separately. Your channel Notify me about preference applies to your own membership. Changing it leaves other members’ preferences unchanged. Agent permissions also belong to the channel. Editing a human member’s organisation role leaves agent permissions unchanged. See What agents can see and do for those controls.
Account removal
Remove user removes workspace access while keeping the account. The account and its data remain. The member action menu can offer Restore access for an inactive account when you hold the required permission. See Remove a member.