Uploaded image for project: 'Identity'
  1. Identity
  2. ID-8059

Ability to uncheck products by default in Product Access when inviting new users

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

      Summary

      All available products are listed and checked by default when inviting a new user.

      There's no way to have them unchecked by default.

      Suggestion

      1. In Product Access settings, provide some way to have certain products unchecked by default or,
      2. Allow the admin to decide which products should not be displayed on the invite screen.

      Workaround (Update: 15 January 2024)

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [ID-8059] Ability to uncheck products by default in Product Access when inviting new users

            George Shaw added a comment - - edited

            cf5de26c352e made a major change to this issue's summary and description, completely changing its scope. She changed "centralized user management" to "original user management". This issue actually affects both forms of user management.

            As other issues opened for centralized (Vortex) user management have been closed as duplicates of this one (e.g. ID-8652), a separate issue should be created for original (non-Vortex) user management rather than repurposing this one.

            This problem is far worse for orgs on Vortex compared to non-Vortex. Atlassian Support can change the defaults for non-Vortex user management, but are unable to do so for Vortex user management (see my previous comment).

            [Edit 2025-03-06: Beverley has now corrected the summary and description to be applicable to both user management experiences.]

            George Shaw added a comment - - edited cf5de26c352e made a major change to this issue's summary and description, completely changing its scope. She changed "centralized user management" to "original user management". This issue actually affects both forms of user management. As other issues opened for centralized (Vortex) user management have been closed as duplicates of this one (e.g. ID-8652 ), a separate issue should be created for original (non-Vortex) user management rather than repurposing this one. This problem is far worse for orgs on Vortex compared to non-Vortex. Atlassian Support can change the defaults for non-Vortex user management, but are unable to do so for Vortex user management (see my previous comment). [Edit 2025-03-06: Beverley has now corrected the summary and description to be applicable to both user management experiences.]

            Noting f45ff7f23a3f's comment, I tried contacting Atlassian Support to ask them to change the default selections for our organisation. Their response stated:

            • We can remove products from being automatically set as the default product when inviting users in the backend, but this feature only applies to non-vortex sites with the (older Atlassian admin hub).
            • Unfortunately, this does not apply to your site since it is on Vortex, the newer Atlassian admin hub.

            George Shaw added a comment - Noting f45ff7f23a3f 's comment, I tried contacting Atlassian Support to ask them to change the default selections for our organisation. Their response stated: We can remove products from being automatically set as the default product when inviting users in the backend, but this feature only applies to non-vortex sites with the (older Atlassian admin hub). Unfortunately, this does not apply to your site since it is on Vortex, the newer Atlassian admin hub.

            Greetings!

            After the general release of JPD, this defect became expensive for many customers due to accidentally adding more Creator licenses.  There are workarounds for JPD using user groups, but I believe the official workaround now is to contact Atlassian Support to ask them to change the default selections for your site when users are created. 

            Please add the support contact as a workaround; perhaps the increased support agent costs will incentivize Atlassian solving this sooner.

            Kind regards,
            Bill

            Bill Sheboy added a comment - Greetings! After the general release of JPD, this defect became expensive for many customers due to accidentally adding more Creator licenses.  There are workarounds for JPD using user groups, but I believe the official workaround now is to contact Atlassian Support to ask them to change the default selections for your site when users are created.  Please add the support contact as a workaround; perhaps the increased support agent costs will incentivize Atlassian solving this sooner. Kind regards, Bill

            This really needs to be looked at - we have added both JPD and JSM in the last 12 months and have to be constantly vigilant that someone hasn't forgotten to uncheck the boxes when adding new users into Jira and Confluence. It's surely such a simple fix and would save a big headache.

            James O'Connor added a comment - This really needs to be looked at - we have added both JPD and JSM in the last 12 months and have to be constantly vigilant that someone hasn't forgotten to uncheck the boxes when adding new users into Jira and Confluence. It's surely such a simple fix and would save a big headache.

            This needs more traction - we have several Atlassian products, but a multitude of different users who certainly dont need default access to all products. Please prioritize this, as it just causes additional and unnecessary admin.

            Warren Kent added a comment - This needs more traction - we have several Atlassian products, but a multitude of different users who certainly dont need default access to all products. Please prioritize this, as it just causes additional and unnecessary admin.

            Best practice for 10+ years in UX design and often even forced as default by law in most countries: Opt-In

            Atlassian: Opt-Out it is

            Michael Kaczor added a comment - Best practice for 10+ years in UX design and often even forced as default by law in most countries: Opt-In Atlassian: Opt-Out it is

            Brad Wood added a comment -

            Adding my vote for this.  We are finding that when inviting new users, Production and Sandbox are checked by default.  We do not necessarily want to grant Sandbox access to all users automatically.  I understand that we can uncheck the box for Sandbox access, but ideally either only Production would be selected by default, or nothing at all, forcing the Admin to make their choices deliberately as to which products should be granted to the new user.

            Will be following this request, and hope to hear an update soon!

            Brad Wood added a comment - Adding my vote for this.  We are finding that when inviting new users, Production and Sandbox are checked by default.  We do not necessarily want to grant Sandbox access to all users automatically.  I understand that we can uncheck the box for Sandbox access, but ideally either only Production would be selected by default, or nothing at all, forcing the Admin to make their choices deliberately as to which products should be granted to the new user. Will be following this request, and hope to hear an update soon!

            how is this possible ? ?? 

            just make it happen ! 

            Dimitri Cools added a comment - how is this possible ? ??  just make it happen ! 

            This is just unbelievable.  I customised the default products under User Access Settings but seems totally pointless and people continue to get invited to products we do not use & do not wish to pay for.  The only way I find out is when I get an Atlassian email telling me my subscription has started!
            There has to be a way to prevent this!
            I'm getting more & more frustrated with recent Atlassian subscription changes and think I've raised more support tickets in the last 6 months than I have in the last 14 years!

            Christine Houlding added a comment - This is just unbelievable.  I customised the default products under User Access Settings but seems totally pointless and people continue to get invited to products we do not use & do not wish to pay for.  The only way I find out is when I get an Atlassian email telling me my subscription has started! There has to be a way to prevent this! I'm getting more & more frustrated with recent Atlassian subscription changes and think I've raised more support tickets in the last 6 months than I have in the last 14 years!

            Unfortunately another dropped ball by Atlassian. My only possible explanation is that we are supposed to add people to the wrong products so we can get a bigger bill. We have a StatusPage trial for 3 people, it is free. But not if someone misses it when trying to add someone to Jira or Confluence. Then we get a bill, Bravo!! We have Analytics, StatusPage and Confluence ticked by default, but not Jira!?!?!?

            Untick them all by default if you can't manage to make it configurable. UI design is supposed to protect the user from mistakes, not help them make them.

            This makes me very grumpy

            Chris Ogden added a comment - Unfortunately another dropped ball by Atlassian. My only possible explanation is that we are supposed to add people to the wrong products so we can get a bigger bill. We have a StatusPage trial for 3 people, it is free. But not if someone misses it when trying to add someone to Jira or Confluence. Then we get a bill, Bravo!! We have Analytics, StatusPage and Confluence ticked by default, but not Jira!?!?!? Untick them all by default if you can't manage to make it configurable. UI design is supposed to protect the user from mistakes, not help them make them. This makes me very grumpy

              gjones@atlassian.com Griffin Jones
              6aa6ce5a27d7 K.Kitajima
              Votes:
              250 Vote for this issue
              Watchers:
              191 Start watching this issue

                Created:
                Updated: