Using repository permissions
Controlling access to code
On this page
Related content
- Merge a pull request
- Remote merge is not happening in Bitbucket Server
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Pull Request is automatically marked merged in Bitbucket Data Center and some of the code changes are lost on target branch after performing conflict resolution in a different branch
- Commits missing from Pull Request merge on target branch
- Automatic branch merging
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- Bitbucket Server is unable to create the merge diff for pull requests
- Keeping forks synchronized
Repository permissions allow you to manage access to a repository for an individual user or a user group beyond that already granted from project permissions.
To modify permissions for a repository
- Go to Settings > Permissions for the repository.
- Click in the Add Users or Add Groups fields in the relevant section to search for, and bulk add, users or groups.
- Choose a permission from the drop-down list, then click Add.
Once added, you can use the checkboxes to edit specific permissions for particular users or groups.
There are three levels of permissions you can grant to a user or group for a repository: Admin, Write and Read.
Browse | Clone, fork, pull | Create, browse or comment on a pull request | Merge a pull request | Push | Edit settings and permissions | |
|---|---|---|---|---|---|---|
| Admin |
|
|  | | | |
| Write |
|
| | |
|  |
| Read |
|
| | | | |
Permissions regarding tasks
- Anyone with permission to browse a pull request can create a task on any comment, and can browse, resolve and reopen existing tasks in the pull request.
- Repository admins and pull request authors can edit and delete any task in the pull request. Reviewers and others can only edit or delete their own tasks.
Granting access to all repositories within a project
If you have a large number of repositories in a project, project level permissions provide a convenient way to grant access to all repositories within that project. For example you can grant a group, say "Team A", Write access at the project level, which will automatically give them Write access to all existing repositories in the project, as well as any repositories that are subsequently created in the project.
To modify permissions for a project, click the Permissions tab when viewing the project. You can add, or modify, permissions for individual users, and groups, in the same way as described above for a single repository.
Granting permission to create repositories
Only users with project administration permission can create new repositories.
Related content
- Merge a pull request
- Remote merge is not happening in Bitbucket Server
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Pull Request is automatically marked merged in Bitbucket Data Center and some of the code changes are lost on target branch after performing conflict resolution in a different branch
- Commits missing from Pull Request merge on target branch
- Automatic branch merging
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- Bitbucket Server is unable to create the merge diff for pull requests
- Keeping forks synchronized