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

As org admin, I want to track license consumption of users my org even if the users are managed in another org

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

      Problem Definition

      As an org admin, my organisation doesn't have an Atlassian Access subscription but I have users that are using Atlassian Access to SSO. I cannot see their license consumption because they are managed by a different org admin on another organization that has an Atlassian Access subscription.

      I'd like to track the number of users who are consuming licenses for Atlassian Access even if they are managed on another org (subscribed to Atlassian Access) by a different org admin.

      Suggested Solution

      Provide a view/tracking of the Atlassian Access users in my organisation

      Workaround

      No workaround at the moment. Only the org admin managing the organisation subscribed to Atlassian Access can view and track licenses consumption.

            [ACCESS-1119] As org admin, I want to track license consumption of users my org even if the users are managed in another org

            Atlassian Update - September 4, 2023

            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 prioritize 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 (no votes or comments 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 in https://jira.atlassian.com as they develop their roadmap, including closed ones. 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!

            Matthew Hunter added a comment - Atlassian Update - September 4, 2023 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 prioritize 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 (no votes or comments 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 in https://jira.atlassian.com as they develop their roadmap, including closed ones. 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!

              Unassigned Unassigned
              6b2430609069 Alexis
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: