Bouncer DocsPermissions
Configure fine-grained access control for team members
Pro plans include fine-grained permissions that let you customize exactly what each team member can access and do. This goes beyond basic roles to give you precise control over your team's capabilities.
Go to Organization Settings > Team, then click the ... menu on any member and select Edit Permissions.
Permission categories
Permissions are organized into categories:
Contacts
| Permission | Description |
|---|---|
| View | See contact list and details |
| Create | Add new contacts |
| Update | Edit contact information |
| Delete | Remove contacts |
| Export | Download contact data |
| Import | Upload contacts from files |
Chat
| Permission | Description |
|---|---|
| View | See conversations and messages |
| Send | Send messages to contacts |
| Assign | Assign conversations to team members |
Instances
| Permission | Description |
|---|---|
| View | See WhatsApp connection status |
| Manage | Change instance settings |
Webhooks
| Permission | Description |
|---|---|
| View | See webhook configurations |
| Manage | Create and edit webhooks |
Campaigns
| Permission | Description |
|---|---|
| View | See campaign list and analytics |
| Manage | Create and edit campaigns |
Workflows
| Permission | Description |
|---|---|
| View | See automation workflows |
| Manage | Create and edit workflows |
Instance access restrictions
Limit which WhatsApp numbers a team member can access:
- In the permissions dialog, find Instance Access
- Select Specific instances
- Check the instances this member should access
- Save changes
Members with instance restrictions only see conversations, contacts, and messages from their allowed WhatsApp numbers. Other instances are completely hidden.
Only view assigned chats
Enable this option to restrict a member to only see conversations assigned to them:
- In the permissions dialog, find the Chat section
- Toggle Only view assigned chats
- Save changes
This creates a focused inbox where team members only see their own work.
Only view created deals
Enable this option to restrict a member to only see CRM deals they created:
- In the permissions dialog, find the CRM section
- Toggle Only view created deals
- Save changes
When enabled:
- Members only see deals they personally created in the CRM pipeline
- Deals created by workflows or automations (assigned to the member) are also visible
- Legacy deals without creator tracking remain visible to all members
- Owners and admins always see all deals regardless of this setting
This is useful for sales teams where each rep should focus on their own pipeline without seeing colleagues' deals.
Role defaults
Each role has default permissions that apply unless overridden:
| Permission | Admin | Member |
|---|---|---|
| Contact: View, Create, Update, Import | Yes | Yes |
| Contact: Delete, Export | Yes | No |
| Chat: View, Send | Yes | Yes |
| Chat: Assign | Yes | No |
| Instance: View | Yes | Yes |
| Instance: Manage | Yes | No |
| Webhook: View | Yes | Yes |
| Webhook: Manage | Yes | No |
| Campaign: View | Yes | Yes |
| Campaign: Manage | Yes | No |
| Workflow: View | Yes | Yes |
| Workflow: Manage | Yes | No |
Admins have full access to all permissions by default.
Common permission setups
Support agent
Give agents a clean, focused inbox with just their assigned conversations:
- Role: Member
- Instance Access: All (or specific if multi-brand)
- Only View Assigned Chats: Enabled
- Chat permissions: View + Send enabled, Assign disabled
Agents see only their work, can respond to customers, but can't reassign conversations.
Multi-brand manager
Restrict access to a specific WhatsApp number for brand separation:
- Role: Member or Admin
- Instance Access: Specific > Select their brand's instance
- All relevant permissions enabled
Manager only sees data from their brand's WhatsApp connection.
Marketing team member
Allow campaign management without touching technical configurations:
- Role: Member
- Campaign: View + Manage enabled
- Webhook: Manage disabled
- Workflow: Manage disabled (or enabled if they handle automations)
Marketer can create campaigns freely without risking webhook or automation changes.
View-only supervisor
Let managers monitor without accidentally messaging customers:
- Role: Member
- Chat: View enabled, Send disabled
- Chat: Assign enabled
Supervisor can review all conversations and distribute work but cannot send customer-facing messages.
External contractor
Minimal access for temporary team members:
- Role: Member
- Instance Access: Specific > Project instance only
- Only View Assigned Chats: Enabled
- Contact: Export disabled
- All Manage permissions: disabled
Contractor works only on assigned conversations from one WhatsApp number, cannot export data or change settings.
Sales representative
Isolate each salesperson's CRM pipeline to focus on their own deals:
- Role: Member
- Only View Created Deals: Enabled
- Pipeline assignments: Only pipelines they work on
Each sales rep sees their own deals in the CRM Kanban board, keeping their view focused and preventing accidental changes to colleagues' deals.
Audit considerations
When setting up permissions, consider:
- Data protection: Disable export permissions for users who don't need to download data
- Separation of concerns: Marketing shouldn't modify webhooks, support shouldn't edit campaigns
- Principle of least privilege: Start restrictive and add permissions as needed
- Instance isolation: Use instance restrictions when managing multiple brands or departments
Upgrade to Pro
Fine-grained permissions require a Pro plan. On free or starter plans, team members use role-based defaults only.
Upgrade your plan to unlock custom permissions.