Built-in roles
Courier has six built-in roles:
On the Developer and Business plans, every teammate is an Administrator, and an invite or API call that sets another role is rejected.
Log access
Each role gets one of three levels of log access:- No logs: the Logs page is empty.
- Timeline only: the message list and each message’s timeline, without event details.
- Full logs: adds the event details, which hold the request data (including PII) and provider responses. Members can also resend and archive messages.
Invite and remove teammates
Administrators invite teammates from Settings → Team: click Invite User, enter their email, and pick a role. To remove someone, use the dropdown next to their email. Teammates join by invitation, or through Okta SCIM provisioning on Enterprise. The Developer plan allows up to 10 pending invites at a time, so accept or revoke one before sending more. Business and Enterprise have no cap.Single sign-on
SSO lets your team sign in through your identity provider. Require SSO to turn off password login.- Google and GitHub SSO: available on every plan. Require sign-in from your configured domains under Settings → Team.
- Okta SSO and SCIM: available on the Enterprise plan. Connect Courier as an app in Okta for sign-in, and use SCIM to create, update, and deactivate users from your directory. Contact Courier to turn them on.
Custom roles
When no built-in role fits, build a custom role from scopes. Each scope pairs a resource with an action, such astemplate:WriteItem. A resource:* wildcard grants every action on that resource, so template:* covers listing, reading, and writing templates.
For example, to give Designers or Analysts log access, create a custom role with the message scopes.
Grant message:ReadEventDetails deliberately. It exposes the request data on each message, including any PII the send carried. message:ListItems and message:ReadItem alone give a timeline-only view.
Platform scopes
Platform scopes cover what the workspace sends:Account-management scopes
Account-management scopes cover the workspace itself:FAQ
Does Courier support role-based access control?
Does Courier support role-based access control?
Courier supports role-based access control (RBAC) with six built-in roles and custom roles on the Enterprise plan. On Developer and Business, every teammate is an Administrator.
Can I create custom roles in Courier?
Can I create custom roles in Courier?
Custom roles are available on the Enterprise plan. You build each one from scopes, such as
template:WriteItem or message:ReadEventDetails, so a role grants exactly the access it needs.How do I give a developer access to Test but not Production?
How do I give a developer access to Test but not Production?
The Developer role has full access in the Test environment and read-only access in Production, with full logs in Test and timeline-only logs in Production.
What can each role see in logs?
What can each role see in logs?
Designer and Analyst see no logs. Developer sees the timeline only in Production and full logs in Test. Administrator, Manager, and Support Specialist see full logs, including event details.
Can I require SSO for my team?
Can I require SSO for my team?
Courier lets you require SSO, which turns off password login. Google and GitHub SSO work on every plan, and Okta SSO is available on Enterprise.
Does Courier support Okta and SCIM?
Does Courier support Okta and SCIM?
Courier supports Okta SSO and SCIM directory provisioning on the Enterprise plan. Contact Courier to turn them on for your workspace.
Does Courier support Microsoft Entra ID?
Does Courier support Microsoft Entra ID?
Microsoft Entra ID support is coming in early Q1 2027. Today, Courier supports SSO through Google, GitHub, and Okta.