Invite Team Members
Synapse supports multiple team members with different levels of access. You can invite colleagues and assign them a role that determines what they can see and do in the dashboard.
Who Can Invite Members
Only users with the Owner or Admin role can invite new team members. If you don't see the invite option, ask your workspace owner or admin to add you.
How to Invite
- Go to Settings in the dashboard sidebar.
- Click Team Members.
- Click Invite Member.
- Enter the person's email address.
- Choose a role from the dropdown (see below for role descriptions).
- Click Send Invitation.
The invited person will receive an email with a link to join your workspace. If they already have a Synapse account, they'll be added immediately. If not, they'll need to create an account first.
Each plan has a member limit. If you've reached your limit, you'll need to upgrade your plan or remove an existing member before inviting someone new. See Billing & Plans for limits.
If the invitation email doesn't send
Inviting someone always adds them to your team as a Pending member, but occasionally the invitation email itself can't be delivered — for example, a temporary email-provider issue or an address that's rejected.
When that happens, Synapse tells you instead of failing silently:
- Right after you invite, you'll see the message "Invite created, but the invitation email could not be sent. You can Resend it from the member's row."
- In the team list, that Pending member is flagged with "Invite email failed — use Resend."
To fix it, click the member's Resend button. Synapse re-sends the invitation and clears the failed flag once the email goes out. You can resend as many times as you need.
The 6 Roles
Synapse has six roles, each with different permissions. Choose the role that best matches what the person needs to do:
| Role | Best For | What They Can Do |
|---|---|---|
| Owner | Workspace creator, account holder | Everything, including billing, plan changes, and workspace deletion |
| Admin | Team leads, managers | Everything except billing and workspace deletion |
| Developer | Engineers, technical staff | Manage flows, templates, segments; view contacts, analytics, and email logs; manage API keys and developer tools |
| Marketing | Marketing team members | Manage flows, templates, and segments; view contacts, analytics, and email logs; export analytics |
| Operations | Support and ops staff | View contacts, email logs, and analytics (read-only) |
| Viewer | Stakeholders, executives | View analytics and flow status only (read-only) |
When in doubt, start with a more restricted role. You can always upgrade someone's role later.
For the full permission matrix, see Team Roles & Permissions.
Managing Existing Members
Change a Role
- Go to Settings > Team Members.
- Find the member in the list.
- Click the role dropdown next to their name.
- Select the new role.
- The change takes effect immediately.
Remove a Member
- Go to Settings > Team Members.
- Find the member in the list.
- Click the Remove button (or the three-dot menu and then "Remove").
- Confirm the removal.
The removed member will lose access to the workspace immediately. They can be re-invited later if needed.
View Pending Invitations
Pending invitations appear at the bottom of the Team Members page. You can:
- Resend an invitation if the person didn't receive it.
- Revoke an invitation if you changed your mind.
Ownership
Every workspace has exactly one owner. The owner has exclusive access to:
- Billing and plan management
- Payment method management
- Workspace deletion
- Ownership transfer
Transferring Ownership
- Go to Settings > Team Members.
- Click Transfer Ownership.
- Select the admin you want to transfer ownership to (only admins are eligible).
- Confirm the transfer.
Transferring ownership is immediate and cannot be undone by the previous owner. The previous owner's role changes to Admin. Make sure you intend to transfer before confirming.
Looking for the API?
If you prefer to manage team members programmatically, see the Members API Reference. For detailed permission matrix by role, see RBAC Documentation.