Free
10
Roles and permissions
Sinkbox uses two separate role systems: one for organisation membership and one for project membership. Both systems share the same role names but are applied and enforced independently.
Note that when you invite a user to a project, they will belong to your organisation (if they are not already a member), but with no role. This means that they will not have access to any other projects until you invite them to another project, or assign them an organisation role.
Total number of users allowed
Starter
100
Pro
100
Business
100
Custom plan: Custom
Organisation roles
Every user who belongs to an organisation has exactly one organisation role.
| Role | Description |
|---|---|
| Admin | Full control over the organisation, including members, billing, and all projects. |
| Developer | Can manage projects and their settings; cannot manage members or billing. |
| Tester | Can interact with inbox items (mark as read, pin, trash); cannot manage projects or members. |
| Reader | View-only access to all organisation projects. |
| Email only | Receives email notifications only; has no application access. |
Permissions
| Capability | Admin | Developer | Tester | Reader | Email only |
|---|---|---|---|---|---|
| View all organisation projects and inboxes | ✓ | ✓ | ✓ | ✓ | ✕ |
| Take inbox actions (mark as read, pin, trash, …) | ✓ | ✓ | ✓ | ✕ | ✕ |
| Create and manage projects | ✓ | ✓ | ✕ | ✕ | ✕ |
| View project settings | ✓ | ✓ | ✕ | ✕ | ✕ |
| Manage API keys for projects | ✓ | ✓ | ✕ | ✕ | ✕ |
| Invite and remove organisation members | ✓ | ✕ | ✕ | ✕ | ✕ |
| Manage project members | ✓ | ✕ | ✕ | ✕ | ✕ |
| Manage public links for projects | ✓ | ✕ | ✕ | ✕ | ✕ |
| Manage billing and plan | ✓ | ✕ | ✕ | ✕ | ✕ |
A user can only hold the Admin role in one organisation at a time. An Admin invitation is rejected if the target user is already an Admin in another organisation. This restriction applies to the organisation role only — a user may still hold the Admin project role on individual projects belonging to other organisations.
Project roles
Project roles are assigned when a user is added directly to a specific project as a guest, or when an organisation member is given an elevated role on a particular project.
| Role | Description |
|---|---|
| Admin | Full control over the project, including managing its members. |
| Developer | Can manage project settings and API keys. |
| Tester | Can interact with inbox items but cannot manage settings. |
| Reader | View-only access to the project inbox. |
| Email only | Receives email notifications for the project; has no application access. |
Permissions
| Capability | Admin | Developer | Tester | Reader | Email only |
|---|---|---|---|---|---|
| View project inbox | ✓ | ✓ | ✓ | ✓ | ✕ |
| Take inbox actions (mark as read, pin, trash, …) | ✓ | ✓ | ✓ | ✕ | ✕ |
| View project settings | ✓ | ✓ | ✕ | ✕ | ✕ |
| Manage API keys | ✓ | ✓ | ✕ | ✕ | ✕ |
| Manage project members and invitations | ✓ | ✕ | ✕ | ✕ | ✕ |
| Manage public links | ✓ | ✕ | ✕ | ✕ | ✕ |
Effective role
When a user has both an organisation role and a project-specific role, the higher rank always takes effect for that project. For example, an organisation-level Tester who is assigned the Developer role on a specific project will have Developer-level permissions on that project.
Role ranks from highest to lowest: Admin › Developer › Tester › Reader › Email only.