Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1608

Allow org admin to control managed users' associated sites and products

    • 52
    • 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.

      We have original feature request https://jira.atlassian.com/browse/ACCESS-1468 to allow org admin to control the managed users' associated products.

      However, according to https://support.atlassian.com/organization-administration/docs/manage-your-users-requests-for-products/ the original feature request will be available in Enterprise plan.

      Non-Enterprise customers are also keen to have this feature. We will suggest to enable this feature for customers with Access subscription in Non-Enterprise plan.

      • Ability to create new sites for Jira, Confluence, JSD
      • Ability to create new Bitbucket or Trello accounts
      • Ability to join sites or products external to the organization
      • Ability to remove managed users from external sites
      • Ability to remove access to specific products

            [ACCESS-1608] Allow org admin to control managed users' associated sites and products

            We truly value your suggestion and the thought you've put into it. The Cloud Enterprise (CE) plan solves the challenges of customers operating our products at a large scale by addressing their complexity, governance, advanced security, and compliance needs. The Atlassian Access product solves for more foundational security requirements and provides identity and access management support. We have implemented solutions for shadow IT risks based on customer differentiation in both CE and Atlassian Access.

            For more information, see https://support.atlassian.com/organization-administration/docs/control-your-shadow-it-footprint/ 

            Thanks for your understanding and for being such an important part of our community!

            Srividya Ramaswamy added a comment - We truly value your suggestion and the thought you've put into it. The Cloud Enterprise (CE) plan solves the challenges of customers operating our products at a large scale by addressing their complexity, governance, advanced security, and compliance needs. The Atlassian Access product solves for more foundational security requirements and provides identity and access management support. We have implemented solutions for shadow IT risks based on customer differentiation in both CE and Atlassian Access. For more information, see https://support.atlassian.com/organization-administration/docs/control-your-shadow-it-footprint/   Thanks for your understanding and for being such an important part of our community!

            Jason Hoddinott added a comment - - edited

            This absolutely needs to be in place. After we ported our on-prem Jira platform to cloud in December, we connected our cloud Windows domain and attached managed users. We discovered after a few billing cycles from Atlassian Access, that active accounts in our AD that had signed up for Trello accounts (we do not use Trello) some as far back as 2016, are getting billed. We have no way, short of an API supplied by support, to remove these billed accounts. Org admins need a way to detach users like this from our bill. 

            Jason Hoddinott added a comment - - edited This absolutely needs to be in place. After we ported our on-prem Jira platform to cloud in December, we connected our cloud Windows domain and attached managed users. We discovered after a few billing cycles from Atlassian Access, that active accounts in our AD that had signed up for Trello accounts (we do not use Trello) some as far back as 2016, are getting billed. We have no way, short of an API supplied by support, to remove these billed accounts. Org admins need a way to detach users like this from our bill. 

            Matt Lane added a comment -

            +1 vote

            Matt Lane added a comment - +1 vote

              Unassigned Unassigned
              2835d42897d7 Emily Q.
              Votes:
              33 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: