Permissions experience brief
Design permissions so people understand, request, grant, and lose access safely.
Product features · 45 min · Advanced · 18 questions
Understanding access
How can people understand their current access?
What should people see before they grant someone more access?
Requests and invitations
Which role should an invitation grant?
Which resource should the invitation cover?
When should the invitation expire?
What context should the invitation give its recipient?
How should people request more access?
Who should approve an access request?
How will the requester learn the outcome?
Denied access
What safe context should a denied user see?
How will denied access preserve unfinished work?
What can a denied user do next?
Permission changes
How should a direct permission conflict be explained?
How should an inherited permission conflict be explained?
How should a group permission conflict be explained?
What happens when access changes while someone is viewing or editing a resource?
Access history
Which permission event should administrators be able to inspect?
Which permission event should an affected user be able to inspect?
How to use this brief
Use this brief as a bank of questions for the conversation. Choose what is relevant, mark covered questions as you go, and skip anything that has already been answered.
Use this brief when...
Use when you need to design permissions so people understand, request, grant, and lose access safely.
Best used as: Live call · Async intake
- Category
- Product features
- Discussion time
- 45 minutes
- Depth
- Advanced
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Live callAsync intake
- Design roles
- Product designer
- Audience
- Product designersProduct managersDesign leadsUX and UI designers
- Platforms
- WebMobileCross-platform
- Company type
- B2BEnterprise
- Product stage
- GrowthMature product
- Tags
- product-featurespermissions-experiencesystems-and-platformsauthorization-uxworkspace-administrationsecure-collaboration