Why this is a UX problem, not just a backend one
Permissions are usually specified as a table of allowed actions. Users experience them as moments of confusion: a missing button, an error, a screen they cannot open. Good design explains the rules at the point where they matter.
Begin with a few roles
| Role | Typical access |
|---|---|
| Owner | Everything, including billing and deleting the account |
| Admin | Manage people and settings, but not ownership |
| Member | Create and edit their own work and shared work |
| Viewer | Read-only access, often for stakeholders |
Four roles cover most teams. Resist the urge to launch with a fully custom permission matrix. Build it when a customer with a real need asks, and design it around the cases they describe.
Make the rules visible
- When an action is not allowed, show the control disabled with a short reason, or explain who can grant access.
- Let people request access from the place they were blocked.
- Show a person's role next to their name in member lists.
- Offer a "view as" preview so admins can check what a role sees.
Handle invitations well
Inviting is the growth loop of most B2B products. Let admins add many people at once, choose the role at invite time, and see the status of each invite. Give invitees a clear first screen that tells them who invited them and what they can do.
Protect the dangerous moments
Removing the last admin, transferring ownership, deleting a workspace: these are rare and costly. Require confirmation that names the consequence, prevent the account from being left without an owner, and keep a log of who did what.



