Is one able to override project permissions at the repo level?

[Andrew]

Hi,

I have a basic understanding of Bitbucket's permission inheritance when it comes to projects and repos.

I have a use case where I would like to override permissions set at the project level, with permissions set at the repo level.

The way I would expect this inheritance to work, is that the most specific permission is the one that is used. I.e., if Project=write and Repo=read, then a user should only have read access, such that the most specific permission takes precedence.

In other words:

If I set write permissions for a user on a project, I would like to potentially also set that user's permission to read on certain repos within the project, such that the repo-level permission overrides the project-level permission for that user.

Is this possible?

[Patrik S · Accepted solution]

Hello @Andrew ,

and thank you for reaching out to Community!

Project permissions inheritance works by assigning the user the highest level of permissions combining the workspace, project, and repository level permissions.

So if a user is part of a group that is assigned Read permissions to a project, but the user was also assigned direct repository Admin permissions, then the user's effective permissions in that particular repository will be the highest of them: Admin permission.

For other repositories within that project where the user was not assigned direct repository permissions, then the Read permissions inherited from the project level will be the effective permissions for the user.

For the scenario you shared where Project=write and Repo=read, the effective permission of the user would be Write - the highest permission of both.

In order to achieve what you're looking for you'd need to configure the other way around:

Set the least permission at the project level, and then assign higher permission for individual users at the repository level (e.g. Project= read, repo = write).

I hope that helps to clarify! Should you have any questions, feel free to ask.

Thank you, @Andrew !

Patrik S