Team and access
Roles and permissions
Use Fetchply role templates and granular permissions to give each teammate only the access they need.
Fetchply defines 23 total permissions. Owners can use workspace roles, agent-level templates, or supported custom roles to apply least privilege.
Templates
- Admin is for broad agent administration.
- Editor manages content, settings, integrations, actions, exports, and replies but cannot delete an agent.
- Viewer has read-only access to core agent, knowledge, conversation, analytics, action, and lead views.
- Support Agent can view the agent, conversations, and leads, and reply to conversations.
All permission keys
| Area | Permissions |
|---|---|
| Agent | chatbot.view, chatbot.edit, chatbot.delete, chatbot.retrain |
| Knowledge | knowledge.view, knowledge.manage |
| Conversations | conversations.view, conversations.reply, conversations.export |
| Analytics | analytics.view, analytics.export |
| Actions | actions.view, actions.manage |
| Leads | leads.view, leads.export |
| WhatsApp campaigns | campaigns.view, campaigns.manage, campaigns.templates, campaigns.send |
| Integrations | integrations.manage |
| Settings | settings.manage |
| Team | team.invite, team.manage_access |
Recommended checks
- Give support staff
conversations.replywithoutchatbot.delete. - Give analysts
analytics.view; addanalytics.exportonly when they may download visitor data. - Reserve
integrations.manage,settings.manage, andactions.managefor trusted operators. - Review agent assignments whenever a member changes role.
- Grant
campaigns.sendexplicitly to people who may launch, schedule or resume marketing broadcasts. Managing drafts alone does not allow sending. System Admins have all three campaign permissions; existing custom roles need an explicit update.
Custom-role availability depends on the controls shown for your workspace and plan.