Linked Repository permissions

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

When configuring a Linked Repository in Bamboo, it's possible to set which users will be able to see and manage it.

Solution

Permission levels

There are two levels of permissions at a Linked Repository level. These are:

  1. Use: this allows for users to utilize the repository in their build plans. It will be visible in the Link existing section when adding a repository to a build plan, as shown below:

    Build plan > Actions > Configure plan > Repositories > Add repository

    (Auto-migrated image: description temporarily unavailable)
  2. Admin: this allows for users to modify the repository configuration through the Linked Repositories admin page. It means that the users will be administrators on that particular repository.

    Cog icon > Linked repositories

    (Auto-migrated image: description temporarily unavailable)

Steps

When adding / configuring a Linked Repository, all you have to do is head to the Permissions tab and configure it according to your needs.

(Auto-migrated image: description temporarily unavailable)

Logged in users

By default, ALL logged in users will have the Use permission set. You can change that (either remove it or make them administrators) in the Others section, at the bottom of the Permissions page. This is useful if you want to set a permission for all users across your instance, since they'll only need to be logged in to be able to use / administrate it.

(Auto-migrated image: description temporarily unavailable)

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.