Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-22182

Provide Granular Admin Access to Non Admins At Repository Level

XMLWordPrintable

    • 4

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Ability to provide non-admins of a repository access to certain admin only areas.

      Ex: Provide Developers access to "admin/addon/admin/pipelines/deployment-settings" , allow non-admins to edit repository variables

      This will help developers who are responsible for deploying services access to environment and deployment variables.
      An option to control this access at a repository level would be beneficial.

            [BCLOUD-22182] Provide Granular Admin Access to Non Admins At Repository Level

            Dylan made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Dylan made changes -
            Labels New: cll-tf3202505

            Dylan added a comment -
            Atlassian Update - May 14, 2025

            Hi everyone,

            Thank you for bringing this Suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap.

            In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management

            Dylan added a comment - Atlassian Update - May 14, 2025 Hi everyone, Thank you for bringing this Suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap . In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management
            SET Analytics Bot made changes -
            Support reference count New: 4

            Alexandre Alencar added a comment -

            I second to that. Having to give developers Admin access just so that they can update a pipeline variable/configuration defeats the whole point of segregation of functions

            Alexandre Alencar added a comment - I second to that. Having to give developers Admin access just so that they can update a pipeline variable/configuration defeats the whole point of segregation of functions
            Swetha Boyapati made changes -
            Description Original: Ability to provide non-admins of a repository access to certain admin only areas.

            Ex: Provide Developers access to "admin/addon/admin/pipelines/deployment-settings"

            This will help developers who are responsible for deploying services access to environment and deployment variables.
            An option to control this access at a repository level would be beneficial.             		New: Ability to provide non-admins of a repository access to certain admin only areas.

            Ex: Provide Developers access to "admin/addon/admin/pipelines/deployment-settings" , allow non-admins to edit repository variables

            This will help developers who are responsible for deploying services access to environment and deployment variables.
            An option to control this access at a repository level would be beneficial.
            ManuA made changes -
            Summary Original: Provide Granular Admin Access to Non Admins New: Provide Granular Admin Access to Non Admins At Repository Level
            ManuA created issue -

              Unassigned Unassigned
              mabraham@atlassian.com ManuA
              Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: