Controlling access to code

Bitbucket Server provides the following types of permissions to allow fully customizable control of access to code.

Note that you can also:

Global permissions

Control user and group access to Bitbucket Server projects and to the Bitbucket Server instance configuration. For example, these can be used to control the number of user accounts that can access Bitbucket Server for licensing purposes.

See Global permissions.

Project permissions

Apply the same access permissions to all repositories in a project. For example, these can be used to define the core development team for a project.

See Using project permissions.

Repository permissions

Extend access to a particular repository for other, non-core, users. For example, these can be used to allow external developers or consultants access to a repository for special tasks or responsibilities.

See Using repository permissions.

Branch permissions

Control commits to specific branches within a repository. For example, these can provide a way to enforce workflow roles such as the Release Manager, who needs to control merges to the release branch.

See Using branch permissions.

Permissions matrix

The table below summarizes the cumulative effect of the permissions described above for anonymous and logged in users. In general, repository permissions override project permissions. A personal project can not be made public.

Key

PermissionEffect
BROWSECan view repository files, clone, pull to local
READCan browse, clone, pull, create pull requests, fork to a personal project
WRITECan merge pull requests
ADMINCan edit settings and permissions
Global
(logged in) 
ProjectRepositoryBranchEffective permission
(error)PersonalPersonalNANo access
(error)PersonalPublic accessNABROWSE just that repo
(error)No accessNo accessNANo access
(error)No accessPublic accessNABROWSE just that repo
(error)Public accessPublic accessNABROWSE all repos in project
(tick)PersonalPersonalNANo access
(tick)PersonalPublic accessNAREAD just that repo
(tick)No accessNo accessNANo access
(tick)No accessPublic accessNAREAD just that repo
(tick)Public accessNo accessNAREAD all repos in project
(tick)Public accessPublic accessNAREAD
(tick)Public accessPublic accessFor this userREAD that branch, no WRITE
(tick)No accessREADNAREAD just that repo
(tick)Public accessREADNAREAD just that repo
(tick)READNo accessNAREAD all repos in project
(tick)READPublic accessNAREAD all repos in project
(tick)READREADNAREAD all repos in project
(tick)READNo accessFor this userREAD that branch, no WRITE
(tick)No accessWRITENAWRITE just that repo
(tick)Public accessWRITENAWRITE just that repo
(tick)WRITENo accessNAWRITE all repos in project
(tick)WRITEWRITENAWRITE all repos in project
(tick)WRITEWRITEFor other usersWRITE to other branches only
(tick)ADMIN  Can edit settings and permissions
Last modified on Feb 11, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.