Permissions for contributors on projects?
I want to give contributor access to specific branches without access to main.
Is this possible?
1 Reply
like-gold•5mo ago
We don't yet support this from the Neon Console, but becuase a branch is an isolated Postgres instance, you can create a branch and provide SQL-only access (i.e., don't give the user Neon Console access, only let them connect via a connection string through an sql client/app)
https://neon.tech/docs/manage/database-access#create-a-developer-role
The other option, but not fool proof, is to use branch protection for your main branch. However, this does not prevent a user from using the SQL Editor or Tables page in the Neon console to make changes to your main branch. When branch protection is enabled, the SQL Editor warns you that a branch is protected. The Tables page does not provide such a warning yet, unfortunately.
https://neon.tech/docs/guides/protected-branches
fyi. Available permissions for Orgs are found here:
https://neon.tech/docs/manage/organizations#user-roles-and-permissions
Neon
Protected branches - Neon Docs
Neon's protected branches feature implements a series of protections Protected branches cannot be deleted. Protected branches cannot be reset. Projects with protected branches cannot be deleted. Compu...
Neon
Manage database access - Neon Docs
Each Neon project is created with a Postgres role that is named for your database. For example, if your database is named neondb, the project is created with a role named neondb_owner. This Postgres r...
Neon
Organizations - Neon Docs
Build your team in Neon with Organizations. Manage all of your team's projects under a single account — with billing, role management, and project collaboration capabilities in one accessible location...