Team & Access
Roles and permissions
The three roles, the reply permission, and how per-app assignments scope what someone sees
Access in ReviewDesk is decided by three things: your role, your assignments, and whether you can reply. They are independent, which is what makes it possible to give a contractor full visibility of one client and no ability to send anything.
Roles
| Role | Scope | Sees |
|---|---|---|
| Organization owner | The whole organization | Everything: dashboard, all apps, team, settings, automation rules, MCP and CLI. |
| Team member | Only their assignments | The reviews inbox and the apps assigned to them. No dashboard, settings, or team screens. |
| Super admin | The whole installation | A separate platform console for whoever operates ReviewDesk — organizations and users across every tenant. |
Assignments
An assignment grants a team member access to either a whole account or a single app. A member can hold many assignments, and they combine — three account assignments means they see every app in all three.
- Account assignment — they see every app in that account, including apps added later
- App assignment — they see exactly that app and nothing else
Assignments filter everything a team member sees — the review list, the counts, the filter facets. An app they are not assigned to is not hidden from view so much as absent from their account entirely.
The reply permission
Can reply is a separate switch from assignments. A member without it can read every review in their assigned apps, and can see drafts, but cannot send anything to a store.
This is the setting for a junior reviewer being trained, an analyst who needs the data but not the outbox, or a client stakeholder you want to give visibility without a voice.
What team members cannot reach
- The dashboard and analytics
- Settings — AI models, tone, alerts, reply footer
- Automation rules
- Team management
- MCP and API access
- Connecting, editing, or deleting apps — they see the app list read-only