Docs / Team, roles and security / Roles: admin and member

Roles: admin and member

Last updated: 16 July 2026

A team member, sometimes called an agent, works the inbox, CRM, and campaigns, and can manage quick replies in Settings. An admin gets everything a member does, plus Automation, and the rest of Settings: team and seats, billing, and WhatsApp channel connections. These limits are enforced on the server, not just hidden in the interface.

What can each role reach?

Area Admin (number connected) Member Admin (no number connected)
Home, Inbox, CRM, Campaigns Yes Yes Home only
Automation Yes No No
Settings: Workspace (team and seats, billing and plan) Yes No No
Settings: Channels (WhatsApp and channels) Yes No Yes
Settings: Messaging (quick replies) Yes Yes No
Help Yes Yes Yes

What can a team member (agent) do?

A member's work area covers Home, Inbox, CRM, and Campaigns, plus Help. In Settings, a member only has the Messaging section, which is where quick replies live. Everything else in Settings, team, billing, channels, stays off their navigation.

This isn't just a hidden menu. Even navigating straight to a settings page's address doesn't get a member the screen behind it: the server checks the role again on every request.

What can an admin do that a member can't?

An admin sees the same work area as a member, plus Automation, where the AI qualifier and auto-replies settings live. In Settings, an admin also reaches Workspace (team and seats, billing and plan) and Channels (WhatsApp and channels). Team and seats is also where your organization's roster is managed, see inviting teammates for how a new person joins.

What changes if my admin hasn't connected a WhatsApp number yet?

An admin without a WhatsApp number connected sees a reduced work area, just Home, plus Help and Settings. Settings for that state only has the Channels section, since connecting a number is the thing to do first. Inbox, CRM, Campaigns, and Automation depend on a connected number and stay out of the navigation until one exists.

Is this enforced, or just hidden in the menu?

Both. The navigation only shows what your role and connection state allow, but the same restriction is checked again on the server for every request, so a member can't reach an admin-only screen by guessing or typing its address directly.

Related

More in Team, roles and security