User Permissions
In SerenDB, roles determine what actions you can take within an organization and its projects. This page provides a detailed breakdown of permissions for each role: Admin, Member, and Collaborator.
For an overview of organizations, see the Organizations page.
Role descriptions
Admin — Full control over the organization and all its projects. Can manage permissions, billing, members, and organization settings. Only Admins can delete organization projects.
Member — Access to all organization projects and can perform most project operations, but cannot modify organization settings or delete projects.
Collaborator — External users invited to specific projects. Collaborators have no organization-level access, but can work on projects they've been invited to.
Organization management
The following table shows what each role can do at the organization level:
Invite organization members
✅
❌
❌
Set organization permissions
✅
❌
❌
Manage organization billing
✅
❌
❌
Rename organization
✅
❌
❌
Delete organization
✅
❌
❌
Enable organization Early Access Program
✅
❌
❌
Project management
The following table shows what each role can do at the project level:
Create new projects
✅
✅
❌
Rename projects
✅
✅
✅
Transfer projects into org
✅
✅
❌
Transfer projects out of org
✅
❌
❌
Delete projects
✅
❌
❌
Manage project databases
✅
✅
✅
Configure project computes
✅
✅
✅
Manage project roles
✅
✅
✅
Invite/remove collaborators
✅
✅
✅
Integration management
The following table shows what each role can do regarding integrations:
Install GitHub integration
✅
❌
❌
Install SerenDB Auth
✅
❌
❌
Install the SerenDB Native Integration on Vercel*
✅
❌
❌
Connect project to GitHub integration
✅
✅
❌
Connect project (SerenDB Postgres Previews Integration)
✅
✅
❌
*SerenDB's native Integration is managed entirely in Vercel and uses Vercel's permission system. For the SerenDB Postgres Previews Integration, projects must first be made available in Vercel before they can be connected to SerenDB.
Notes and limitations
Branch management — All users are currently able to manage protected branches, regardless of their role or permission level. Granular permissions for this feature are not yet implemented.
Permissions and roles — The current permissions system may not meet all needs for granular control. Share your feedback and requirements for more detailed permissions settings via the Feedback form or our Discord feedback channel.
Last updated