User Roles
Last updated: April 12, 2026
Last Updated: April 12, 2026
Access & Permissions Guide
Overview
User Roles control what each teammate can see and manage inside Sendblue. If a tab, integration, or settings area looks missing for one user but visible for another, role access is one of the first things to check.
Role summary
| Role | Best fit | Typical access |
|---|---|---|
| Admin | Account owners, operators, or trusted system admins | Full platform access, integrations, system settings, team management, and automation building. |
| Manager | Team leads who need broad visibility without being the main system owner | Can view all conversations and help manage the team, but may not have every admin-level configuration responsibility. |
| User | Individual reps who should stay focused on their assigned work | Can view and manage assigned conversations rather than the full account. |
How to choose the right role
Use Admin for the smallest possible group of people who genuinely need configuration power.
Use Manager when someone needs broad team visibility but should not be your default account-wide admin.
Use User for day-to-day reps who only need their assigned conversations and should not change account-wide setup.
Common permission misunderstandings
If a user cannot see API Settings, Integrations, or another account-level tab, check their role before assuming the feature is broken.
A manager seeing all conversations does not automatically mean they should be used for every admin task.
Giving everyone Admin access usually creates more risk and confusion than speed.
If multiple teammates are testing the same issue, compare what each person can see before treating it as a product bug.
Recommended access review
List which teammates actually need account-wide settings access.
Confirm who needs all-conversation visibility versus assigned-conversation visibility only.
Keep automation, integrations, and API credentials in the hands of trusted admins.
Re-check roles whenever a new teammate says a settings page or feature is missing.
How to verify role access is correct
Have the user sign in and check the exact page they need.
Compare that experience against a known admin seat.
If the admin can see the feature but the other user cannot, review the role before escalating.
After the role is updated, refresh the session and confirm the expected tabs and views now appear.