Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-18825

Availability to manage permissions on the Organizations you have access

XMLWordPrintable

    • 0

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

      Availability to manage permissions on the Organizations you have access based on the Admin of the instance

            [JSWCLOUD-18825] Availability to manage permissions on the Organizations you have access

            Matthew Hunter added a comment -
            Atlassian Update - January 5, 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 - January 5, 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!

            Jake Wills added a comment -

            As it currently works, any instance admin can add an email domain to allow people with those email addresses to self-enroll. For another instance registered with that email domain, it also adds to the navigation an option to join the first instance for all users. As the administrator of an instance, I need the ability to control what other instances my users are prompted to join by navigation options. If they are invited to join another instance directly, that is fine, but prompting them to do so by adding it to my instance navigation is not ok.

            This is a foundational principle of multi-tenant SaaS platforms. Do not allow what others do in their instance to impact my instance or users without coordination and mutual approval. Aside from the potential operational impacts, this is a security concern that creates liability for both organizations. Without control, the current state is creating liability for my organization that I can not control or mitigate. Please take this seriously.

            Jake Wills added a comment - As it currently works, any instance admin can add an email domain to allow people with those email addresses to self-enroll. For another instance registered with that email domain, it also adds to the navigation an option to join the first instance for all users. As the administrator of an instance, I need the ability to control what other instances my users are prompted to join by navigation options. If they are invited to join another instance directly, that is fine, but prompting them to do so by adding it to my instance navigation is not ok. This is a foundational principle of multi-tenant SaaS platforms. Do not allow what others do in their instance to impact my instance or users without coordination and mutual approval. Aside from the potential operational impacts, this is a security concern that creates liability for both organizations. Without control, the current state is creating liability for my organization that I can not control or mitigate. Please take this seriously.

              kbui Kevin Bui
              falfaro@atlassian.com Fabian A
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: