The tables below summarize permissions by project role. A higher role has every permission of the roles below it, in the order Viewer < Editor < Admin < Owner. All permission checks run on the server. The interface hides unavailable buttons only for convenience.
Legend: ✓ allowed; No: not allowed; ◐ allowed under conditions (see Notes).
| Action | Owner | Admin | Editor | Viewer |
|---|
| Sign in, change own password | ✓ | ✓ | ✓ | ✓ |
| Open Organization admin | ✓ | No | No | No |
| Create, edit, delete users; reset passwords | ✓ | No | No | No |
| Create and delete projects | ✓ | No | No | No |
| Rename a project | ✓ | ✓ | No | No |
| Projects visible | All projects | Linked projects | Linked projects | Linked projects |
| Action | Owner | Admin | Editor | Viewer |
|---|
| Add and remove members; change roles; manage groups | ✓ | ✓ | No | No |
| Set an action’s permission mode and grant run access | ✓ | ✓ | No | No |
| Add and rename environments; production flag; IP allowlist | ✓ | ✓ | No | No |
| Change environment access; grant/revoke access | ✓ | ✓ | No | No |
Enter a restricted environment | ✓ | ✓ | ◐ ¹ | ◐ ¹ |
| Pick an environment in the top bar | ✓ | ✓ | ✓ | ✓ |
| View the Audit log and export it as CSV | ✓ | ✓ | No | No |
| Action | Owner | Admin | Editor | Viewer |
|---|
| See the project Overview page | ✓ | ✓ | ✓ | No |
| See data sources, config (without passwords), tables & diagram | ✓ | ✓ | ◐ ² | No |
| Test the saved connection | ✓ | ✓ | ◐ ² | No |
| Add, edit, delete data sources; save connections; test a typed config | ✓ | ✓ | No | No |
| See, add, edit, delete variables and secrets | ✓ | ✓ | ◐ ² | No |
| See SQL; create, edit, publish, roll back actions | ✓ | ✓ | ✓ | No |
| Create CRUD actions from a table | ✓ | ✓ | ◐ ² ³ | No |
| Turn environments on/off for actions, views, schedules | ✓ | ✓ | ◐ ² | No |
| Delete actions | ✓ | ✓ | No | No |
| Create, edit, publish, roll back, delete views | ✓ | ✓ | ✓ | No |
| Preview a view | ✓ | ✓ | ◐ ² | No |
| Action | Owner | Admin | Editor | Viewer |
|---|
| Run actions, run in the background, bulk run | ◐ ⁴ | ◐ ⁴ | ◐ ⁴ | ◐ ⁴ |
| Open screens (published views) | ✓ | ✓ | ✓ | ✓ ⁵ |
| See run history | Everyone’s | Everyone’s | ◐ ² | Own runs |
| See and cancel jobs | All jobs | All jobs | ◐ ² | Own jobs |
| Create, edit, enable, delete schedules | ✓ | ✓ | ◐ ² | No |
| Export run results as CSV | ◐ ⁴ | ◐ ⁴ | ◐ ⁴ | ◐ ⁴ |
- Owners and admins always have access to every environment. Editors and Viewers enter a
restricted environment when granted directly or through a group. In an open environment, every member has access.
- Requires the Editor role in the selected environment. In a restricted environment where the granted maximum role is
viewer, a project Editor has only Viewer rights: run actions and see their own runs. See Roles.
- Editors can create CRUD actions with the default run access or with access open to every member. Granting access to specific people and groups requires the Admin role.
- Allowed when the action is published, enabled in the selected environment, and the person has permission on it. Every member can run an
open action. Only granted members and groups can run a restricted action, and this applies to owners and admins as well. The environment’s IP allowlist and rate limits also apply. Background and bulk runs are only available for SQL actions in Writes data mode.
- Screens list only the views enabled in the selected environment. Each action that a screen calls is still checked separately against the viewer’s own permissions.