Team Roles & Permissions
Synapse has six roles that control what each team member can see and do. Every member is assigned exactly one role, and permissions are enforced across the entire dashboard.
Role Overview
| Role | Description | Best For |
|---|---|---|
| Owner | Full access to everything, including billing and workspace management | The person responsible for the account |
| Admin | Full CRM access plus team management, but no billing | Team leads and managers |
| Developer | CRM features plus developer tools and system settings | Engineers and technical staff |
| Marketing | Flows, templates, segments, and analytics | Marketing team members |
| Operations | Read access to contacts, email logs, and analytics | Support and operations staff |
| Viewer | Analytics only (read-only) | Stakeholders and executives |
Permission Matrix
The table below shows exactly what each role can do. A checkmark means the role has that permission.
Flows
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View flows | Yes | Yes | Yes | Yes | -- | -- |
| Create and edit flows | Yes | Yes | Yes | Yes | -- | -- |
Templates
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View templates | Yes | Yes | Yes | Yes | -- | -- |
| Create and edit templates | Yes | Yes | Yes | Yes | -- | -- |
Segments
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View segments | Yes | Yes | Yes | Yes | -- | -- |
| Create and edit segments | Yes | Yes | Yes | Yes | -- | -- |
Analytics
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View analytics | Yes | Yes | Yes | Yes | Yes | Yes |
| Export analytics (CSV) | Yes | Yes | -- | Yes | -- | -- |
Contacts
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View contact list | Yes | Yes | Yes | Yes | Yes | -- |
| Edit contacts | Yes | Yes | -- | -- | -- | -- |
Email Logs
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View email logs | Yes | Yes | Yes | Yes | Yes | -- |
Developer Tools
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View API keys | Yes | Yes | Yes | -- | -- | -- |
| Manage API keys | Yes | Yes | Yes | -- | -- | -- |
| View sender domains | Yes | Yes | Yes | -- | -- | -- |
| Manage sender domains | Yes | Yes | -- | -- | -- | -- |
| Dev tools | Yes | Yes | Yes | -- | -- | -- |
Settings
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View settings | Yes | Yes | Yes | -- | -- | -- |
| Modify settings | Yes | Yes | Yes | -- | -- | -- |
| Team management | Yes | Yes | -- | -- | -- | -- |
Billing & Workspace (Owner Only)
| Permission | Owner | Admin | Developer | Marketing | Operations | Viewer |
|---|---|---|---|---|---|---|
| View billing | Yes | -- | -- | -- | -- | -- |
| Manage billing | Yes | -- | -- | -- | -- | -- |
| View payment methods | Yes | -- | -- | -- | -- | -- |
| Manage payment methods | Yes | -- | -- | -- | -- | -- |
| View invoices | Yes | -- | -- | -- | -- | -- |
| Delete workspace | Yes | -- | -- | -- | -- | -- |
| Transfer ownership | Yes | -- | -- | -- | -- | -- |
The Owner role is unique -- there is exactly one owner per workspace, and they cannot be removed. Ownership can only be transferred to an existing Admin. See Invite Team Members for details on ownership transfer.
Role Differences Explained
Owner vs Admin
The Owner has everything the Admin has, plus exclusive access to billing, payment methods, invoices, workspace deletion, and ownership transfer. If you need someone to manage the team but not handle payments, make them an Admin.
Admin vs Developer
Both can manage flows, templates, and segments. The Admin additionally has team management (inviting and removing members, changing roles) and can edit contacts. The Developer has read-only contact access but also has API key management, developer tools (DLQ viewer, event schemas), and system settings -- which the Admin also shares.
Developer vs Marketing
The Developer has access to developer tools (DLQ, event schemas), API key management, system settings, and contact read access. Marketing can manage flows, templates, and segments, and has analytics export capability, but cannot access developer tools or system settings.
Marketing vs Operations
Marketing can create and edit flows, templates, and segments, and export analytics. Operations has a much narrower scope: read access to contacts, email logs, and analytics only. Operations cannot view flows, templates, or segments. Operations is designed for support staff who need to look up specific contacts and email delivery records.
Operations vs Viewer
Operations can see contacts, email logs, and analytics. Viewers can only see analytics dashboards -- nothing else.
Changing Roles
Only Owners and Admins can change team members' roles:
- Go to Settings > Team Members.
- Find the member.
- Click the role dropdown and select the new role.
- The change takes effect immediately.
Be careful when changing someone from Admin to a more restricted role. They will immediately lose access to team management and any other permissions they previously had.