• 10
    • 0
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      At the moment, when the number of users with can use permission in Confluence exceeds the user limit in the license, all users become read-only until the problem get fixed.

      We could have a less disruptive approach to let licensed users work in Confluence. Two possible options are:

      • Only new added users over the license limit are read-only.
      • No users can be added (or received from an external user directory) over the license limit.

      The sysadmins should receive a clear notification of this once they reach the user limit and even a warning if they are near to reach it (i.e.: 90% total user capacity).

            [CONFSERVER-27524] Exceed user limit should not make all users read-only

            Stephen HJ added a comment -

            Hi Mike, thank you so much for the update and positive feedback. Hope to see the updated roadmap soon.  

            Stephen HJ added a comment - Hi Mike, thank you so much for the update and positive feedback. Hope to see the updated roadmap soon.  

            Hi,

            The Atlassian Data Center team acknowledges that this issue is causing major friction for some of our customers.

            We are in the process of planning our development of solutions for Data Center products, including but not limited to: first, a license utilization warning notification feature, and then features to automatically block adding new users when the licensed seat ceiling is reached, and more.

            Further details about these solutions will be provided once they are ready. Please stay tuned and follow our Data Center public roadmap for upcoming updates.

            Feel free to leave your comments here so that we can continuously listen to your feedback.

            Regards

            Atlassian Data Center Team

            Xiaoxiang (Mike) Ni added a comment - Hi, The Atlassian Data Center team acknowledges that this issue is causing major friction for some of our customers. We are in the process of planning our development of solutions for Data Center products, including but not limited to: first, a license utilization warning notification feature, and then features to automatically block adding new users when the licensed seat ceiling is reached, and more. Further details about these solutions will be provided once they are ready. Please stay tuned and follow our Data Center public roadmap for upcoming updates. Feel free to leave your comments here so that we can continuously listen to your feedback. Regards Atlassian Data Center Team

            Stephen HJ added a comment -

            This design has causes the internal incident several times, could you please change the design? Having 20,000 users impact because just 1 additional user over license doesn't make sense at all. 

            Stephen HJ added a comment - This design has causes the internal incident several times, could you please change the design? Having 20,000 users impact because just 1 additional user over license doesn't make sense at all. 

            The Data Center team is considering providing better license utility management to prevent such situations happens to DC products. Stay tunned.

             

            Regards

            Atlassian Data Center team

            Xiaoxiang (Mike) Ni added a comment - The Data Center team is considering providing better license utility management to prevent such situations happens to DC products. Stay tunned.   Regards Atlassian Data Center team

            Richard Cross added a comment - - edited

            From a commerical point of view, I can see exactly why this hasn't been addressed over 13 years later: it creates a powerful incentive for customers to upgrade their license.

            It's an abysmal customer/end-user experience of course, but that's beside the point.

            Richard Cross added a comment - - edited From a commerical point of view, I can see exactly why this hasn't been addressed over 13 years later : it creates a powerful incentive for customers to upgrade their license. It's an abysmal customer/end-user experience of course, but that's beside the point.

            Chuck V added a comment -

            IMHO, This type of license enforcement is a great way to send your customers RUNNING away from your product.
            You're going to set us up for failure by allowing over-provisioning but then SHUTTING OUT ALL USERS including the ones we paid for!?!?

            Very Very poor customer service there Atlassian. please fix this quickly... If we can't I fear that my company will seek solutions from your competitors, with more friendly enforcement of license limits.

            Chuck V added a comment - IMHO, This type of license enforcement is a great way to send your customers RUNNING away from your product. You're going to set us up for failure by allowing over-provisioning but then SHUTTING OUT ALL USERS including the ones we paid for!?!? Very Very poor customer service there Atlassian. please fix this  quickly... If we can't I fear that my company will seek solutions from your competitors, with more friendly enforcement of license limits.

            The current Jira Software server behavior is simply unacceptable... we are in production with hundreds of active users that suddenly are forced to stop their work if just 1 more user is added. It's really incredible that in 2021 Jira Software server still continue to work in this way... 

            Mario Genovese added a comment - The current Jira Software server behavior is simply unacceptable... we are in production with hundreds of active users that suddenly are forced to stop their work if just 1 more user is added. It's really incredible that in 2021 Jira Software server still continue to work in this way... 

            I've also just had to scramble to restore confluence to a usable state after extra users logged in via LDAP. The current behaviour is unacceptable. I'd vote for the "No users can be added (or received from an external user directory) over the license limit." option

             

             

            Richard Lavey added a comment - I've also just had to scramble to restore confluence to a usable state after extra users logged in via LDAP. The current behaviour is unacceptable. I'd vote for the "No users can be added (or received from an external user directory) over the license limit." option    

            Hello guys!

            We had our Conlfuence in read-only mode because one new user has been created automatically and broke our instance.

            I totally agree reporter - it should be forbidden to create and/or enable new user if license limit has been hit.

             

            We already have monitoring for user count and don't enable/create manually, but automatically created user absolutely surprised us :-/

             

            Thanks,

            Ivan

            Ivan Punko added a comment - Hello guys! We had our Conlfuence in read-only mode because one new user has been created automatically and broke our instance. I totally agree reporter - it should be forbidden to create and/or enable new user if license limit has been hit.   We already have monitoring for user count and don't enable/create manually, but automatically created user absolutely surprised us :-/   Thanks, Ivan

            Thanks for your interest in this issue.

            This request is considered a potential addition to our longer-term roadmap.
            We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. Cheers, Confluence Product Management

              a36bb1a6a1fa Xiaoxiang (Mike) Ni
              aconde Alejandro Conde Carrillo (Inactive)
              Votes:
              62 Vote for this issue
              Watchers:
              52 Start watching this issue

                Created:
                Updated: