An admin has full access to every screen and permission in the workspace. A team member, sometimes called an agent, starts with the everyday screens and Lead CRM. An admin can then grant or revoke extra permissions for that member. Admin-only screens stay admin-only, whatever permissions a member has.
Member (default) is what a newly invited member starts with. Member (if granted) is what that member can reach after an admin turns on the permission named in parentheses. A Yes in both member columns means the screen does not need an extra permission. An admin-only screen stays No even when a related permission is granted.
| Screen or feature | Admin | Member (default) | Member (if granted) |
|---|---|---|---|
| Home: Overview | Yes | Yes | Yes |
| Home: Analytics (Reports & analytics) | Yes | No | Yes |
| Home: Leaderboard (Reports & analytics) | Yes | No | Yes |
| Home: Reports | Yes | No | No |
| Inbox | Yes | Yes | Yes |
| CRM: Pipeline (Lead CRM) | Yes | Yes | Yes |
| CRM: Forms | Yes | No | No |
| Contacts | Yes | Yes | Yes |
| Campaigns: Send a campaign (Broadcasts & campaigns) | Yes | No | Yes |
| Campaigns: Drip campaigns (Broadcasts & campaigns) | Yes | No | Yes |
| Campaigns: Abandoned carts (Broadcasts & campaigns) | Yes | No | Yes |
| Automation: Flows | Yes | No | No |
| Automation: Auto-replies | Yes | No | No |
| Automation: AI Qualifier | Yes | No | No |
| Help | Yes | Yes | Yes |
| Profile | Yes | Yes | Yes |
| Settings | Yes | Yes | Yes |
| Settings: Team & seats | Yes | No | No |
| Settings: Notifications | Yes | Yes | Yes |
| Settings: Billing & plan | Yes | No | No |
| Settings: Data export | Yes | No | No |
| Settings: Integrations | Yes | No | No |
| Settings: WhatsApp & channels | Yes | No | No |
| Settings: Website widget | Yes | No | No |
| Settings: Product catalog | Yes | Yes | Yes |
| Settings: Payments | Yes | No | No |
| Settings: Quick replies | Yes | Yes | Yes |
| Settings: Templates | Yes | Yes | Yes |
| Settings: Meta Flows | Yes | Yes | Yes |
| Settings: Data fields | Yes | No | No |
| Settings: Developer | Yes | No | No |
Whether a WhatsApp number is connected does not change this table. It changes only what a few number-dependent screens show, see below.
A permission is something an admin can turn on or off for one member. The six available permissions are:
Stravax AI studio opens in the separate Stravax AI workspace, so it does not have a row in the screen table above.
A new member starts with Lead CRM. The other five permissions start off. This does not remove screens that every member can reach, such as Inbox, Contacts, Help, Profile, and the member Settings screens shown above.
An admin can choose permissions while sending an invitation. To change them later, open Settings, then Team & seats. Find the member, select Manage access, turn permissions on or off, then select Save. This screen also controls which connected channels that member can work in.
Nothing extra is hidden. Before a number is connected, every screen allowed by your role and permissions stays in the navigation. You can still prepare the workspace before connecting a number.
A handful of screens genuinely need a number to do their job. Those show a short connect-your-number card in place of the screen rather than an error. An admin gets a button to the connect flow. A member who can reach that screen gets a note to ask an admin. The screens that do this are Inbox, Campaigns and its tabs, Settings then Messaging then Templates, and Settings then Channels then Website widget. Everything else works as normal.
Both. The navigation only shows what your role and permissions allow, and the server checks the same rules again where it matters: admin-only changes and permission-gated features are refused even if a request skips the menu. A member cannot reach an admin-only screen by guessing or typing its address directly, and turning off a permission blocks the related features too.