Hello Atlassian team,
We are currently investigating user management behavior for organizations using the Organizations REST API.
At the moment, we understand that Org API v2 supports user suspension and removal for both original user management and centralized (new) user management. However, we could not find an explicit API or response field that indicates which user management mode an organization is using.
We would like to confirm the following points:
Is there any official API or response property that explicitly identifies whether an organization uses original user management or centralized (new) user management?
We noticed that some Organizations APIs expose additional response fields such as added_to_org only when the new user management experience is enabled. Can this behavior be considered a reliable and supported indicator of centralized user management?
Is this behavior guaranteed to remain stable long term, or could these response fields change without notice?
If there is currently no supported way to determine the user management type via API, are there any plans to expose this information in the future?
This information is important for us to handle organization-level user management logic correctly and safely.
Thank you for your support.
Hi @Leo Nguyen
No, there isn't an API that answers this question. Alternatively, this is how the user management is being managed:
|
|
Original user management |
Centralized user management |
|---|---|---|
|
User management |
Can manage the users, groups, and administration settings of the site they’ve been assigned to. |
Can access Atlassian Administration(admin.atlassian.com) and complete tasks related to the specific site they are administering. This includes adding new products to the site and managing apps installed on the site. |
|
Permissions |
Can freely invite users or modify users based on their requirements within the site they administer. |
Can’t invite or modify any users even within the site they administer. However, if Site Admins wish to, then it is possible to combine the Site Admin and the User Access Admin roles (Dual permission as mentioned here.) |
|
Log in as another user |
Can impersonate other users via the “Log in as user” option. |
Can’t impersonate other users. This option will be locked for the Site Admin. Only an Org Admin can log in as another user. |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Leo Nguyen
As you provided the same question last Sunday in multiple forum categories.
If there is no direct answer, people might no have one, or redirect your answer to Atlassian Support
and
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Marc -Devoteam- Please keep this question and delete the other one that is not allowed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.