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

Include the multiple Identity providers feature in the Atlassian Guard plans

XMLWordPrintable

    • 3

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

      Current behavior

      Currently, the ability to connect multiple identity providers is available to customers on enterprise plans.

      Suggestion

      It would be beneficial to have this feature included directly in the Atlassian Guard plans

      Why is this important

      There are some customers of Atlassian products that would benefit from this feature being purchasable standalone, outside of an enterprise subscription

            [ACCESS-1942] Include the multiple Identity providers feature in the Atlassian Guard plans

            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2

            Aaron Short added a comment -

            We were told verbally (and it seems mistakenly) that we could use Atlassian Guard on the Premium plan to connect to multiple IDPs, despite the literature stating that Enterprise was required. We were shocked and disappointed to find out that is not true. I'm sure it was a simple misunderstanding, but it is having a huge impact on multiple projects for our organization.

            We have scrambled to put some instructions together for our affected, internal customers, and we're launching the first of the projects tonight without SSO. The sooner we can get this feature, the better!

            Aaron Short added a comment - We were told verbally (and it seems mistakenly) that we could use Atlassian Guard on the Premium plan to connect to multiple IDPs, despite the literature stating that Enterprise was required. We were shocked and disappointed to find out that is not true. I'm sure it was a simple misunderstanding, but it is having a huge impact on multiple projects for our organization. We have scrambled to put some instructions together for our affected, internal customers, and we're launching the first of the projects tonight without SSO. The sooner we can get this feature, the better!
            SET Analytics Bot made changes -
            Support reference count New: 1
            Uchechi I made changes -
            Description Original: h3. Current behaviour
            Currently, the ability to [connect multiple identity providers|https://support.atlassian.com/provisioning-users/docs/supported-identity-providers/#Connecting-multiple-identity-providers] is available to customers on enterprise plans.

            h3. Suggestion
            It would be beneficial to have this feature included directly in the Atlassian Guard plans

            h3. Why is this important
            There are some customers of Atlassian products that would benefit from this feature being purchasable standalone, outside of an enterprise subscription             		New: h3. Current behavior
            Currently, the ability to [connect multiple identity providers|https://support.atlassian.com/provisioning-users/docs/supported-identity-providers/#Connecting-multiple-identity-providers] is available to customers on enterprise plans.

            h3. Suggestion
            It would be beneficial to have this feature included directly in the Atlassian Guard plans

            h3. Why is this important
            There are some customers of Atlassian products that would benefit from this feature being purchasable standalone, outside of an enterprise subscription
            Uchechi I created issue -

              rheda FellowJitster
              e32c3a85cf21 Uchechi I
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: