Workspaces and collaborator permissions
Workspaces group databases and developer access. The owner creates the workspace; other developers can be members or admins. A display name must contain at least two characters.
Current role behavior
All protected operations also require account/subscription access. This table describes the reviewed management behavior; native database users have their own independent permissions.
| Operation | Member | Admin | Owner |
|---|---|---|---|
| Read workspace/database metadata, users, metrics, audit | Yes | Yes | Yes |
| Browse tables/collections/keys | Yes | Yes | Yes |
| PostgreSQL editor reads | Yes | Yes | Yes |
| PostgreSQL editor writes; Redis/MongoDB editor commands | No | Yes | Yes |
| Create, pause, resume, clone databases (where supported) | No | Yes | Yes |
| Read privileged connection details; manage database users | No | Yes | Yes |
| Change database metadata/network policy; delete database | No | No | Yes |
| Create, delete or restore manual backups | Yes | Yes | Yes |
| Manage or trigger backup schedules | No | Yes | Yes |
| Manage members; edit/deactivate workspace | No | No | Yes |
A member is therefore not a universal read-only role. In particular, backup deletion and restore can change recovery state or overwrite data. Give workspace membership only to developers trusted with those operations.
Add collaborators
The owner can add an existing developer by account ID and choose member or admin. Developer search requires at least three query characters and returns at most five matches. Verify the intended account before adding it. Membership creation is direct and does not require an accepted invitation.
The invitation endpoints record pending invitations, with a seven-day expiry, and support cancellation. The current API does not provide invitation acceptance or a complete invitation email workflow. If the dashboard offers an invitation action, do not assume that recording an invitation grants membership; confirm the member list. Use the supported membership operation where available, or contact support if the UI cannot complete it.
Role-change/removal URLs require the membership record UUID, not the developer account ID. The owner’s membership cannot be changed or removed through these operations.
Retire a workspace
Deactivating a workspace changes its active flag. It does not by itself prove that its databases were deleted. Explicitly manage database lifecycle and recovery before retiring the workspace.