Versions
- 9.5
- 9.4
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- 4.14
- 4.13
- 4.12
- See all
Allowing public access to code
Controlling access to code
On this page
Related content
- Committing plan changes
- Settings estimates with story points
- Creating and editing a new plan
- Creating and deleting plans
- Discovering Portfolio for Jira
- Getting started with Portfolio for Jira
- Portfolio for Jira FAQs
- Configuring initiatives and other hierarchy levels
- Creating and deleting issues
- Configuring plan settings
You can open up public access for anonymous (unauthenticated) users to projects and repositories in Bitbucket Server. This allows you to:
- Broadcast your repositories to a wider audience who generally don't have access to your source.
- Utilize unauthenticated cloning of repositories when setting up continuous integration servers to work with Bitbucket Server.
- Link from other systems, for example JIRA applications or Confluence, to give users access to code without requiring authentication.
- Create open-source projects or repositories.
Public access allows anonymous users to browse the files, pull requests and commits for a specific repository or an entire project, and to clone repositories, without needing to log in, or have an account in Bitbucket Server.
In Bitbucket Server, you can:
- Configure a specific repository for public access.
- Configure a project to allow public access to all repositories in the project.
- Disable anonymous access by setting a global system property.
Making a repository publicly accessible
You can open up a specific repository for public (anonymous) access.
You need admin permission for the repository.
Go to the repository and click Settings, then Repository (under 'Permissions'). Check Enable (under 'Public Access') to allow users without a Bitbucket Server account to clone and browse the repository.
Making a project publicly accessible
You can open up a whole project (but not a private project) for public (anonymous) access.
You need admin permission for the project.
Go to the project and choose Settings, then Permissions. Check Enable (under 'Public Access') to allow users without a Bitbucket Server account to clone and browse any repository in the project.
Viewing public repositories
Bitbucket Server displays a list of repositories for which anonymous access has been enabled.
Anonymous and logged-in users can choose Repositories > View all public repositories to see these.
Disabling public access globally
Bitbucket Server provides a system property that allows you to turn off public access for the whole instance.
To do this, set the feature.public.access property to false in the bitbucket.properties file in your Bitbucket Server home directory.
Related content
- Committing plan changes
- Settings estimates with story points
- Creating and editing a new plan
- Creating and deleting plans
- Discovering Portfolio for Jira
- Getting started with Portfolio for Jira
- Portfolio for Jira FAQs
- Configuring initiatives and other hierarchy levels
- Creating and deleting issues
- Configuring plan settings