Details
-
Suggestion
-
Resolution: Answered
-
5
-
Description
Atlassian's response for closure:
Hello everyone,
For all the watchers of this request, upon performing different tests and working in recent, existing scenarios for Confluence Cloud, the behavior of this suggestion should be applied for the Confluence Server/On-prem edition, highlighted in the following sources:
- What happens when I reach my license user limit in Confluence
- https://jira.atlassian.com/browse/CONFSERVER-27524 (original suggestion where this was cloned from)
For Confluence Cloud, the behavior is already different, impacting the customization for spaces and creating new personal spaces as well, as described in the following public article:
As the impact should not turn Confluence into read-only, allowing pages to be edited and created, we will be closing this suggestion, but the corresponding one for Confluence Server/On-prem will remain open to collect feedback.
To improve the handling of Annual subscriptions for Atlassian Cloud, the following suggestion has been created, which you can add yourself as a watcher and share feedback:
https://jira.atlassian.com/browse/ID-8076
Thank you very much for your patience!
Current
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 gets fixed.
We could have a less disruptive approach to let licensed users work in Confluence.
Suggestion
Two possible options are:
- Only newly 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).
Attachments
Issue Links
- is duplicated by
-
- Closed
- is related to
-
- Under Consideration
- relates to
-
- Closed