# How can I check the error "Organization: is not with the new user management experience"

**URL:** <https://community.developer.atlassian.com/t/how-can-i-check-the-error-organization-is-not-with-the-new-user-management-experience/102939>\
**Category:** Forge\
**Tags:** rest-api, atlassian-connect\
**Created:** [September 28, 2026, 9:00am UTC](https://community.developer.atlassian.com/t/how-can-i-check-the-error-organization-is-not-with-the-new-user-management-experience/102939 "2026-09-28T09:00:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuanming](https://avatars.discourse-cdn.com/v4/letter/y/a698b9/32.png) [@yuanming](https://community.developer.atlassian.com/u/yuanming)\
**Post date:** [September 28, 2026, 9:00am UTC](https://community.developer.atlassian.com/t/how-can-i-check-the-error-organization-is-not-with-the-new-user-management-experience/102939/1 "2026-09-28T09:00:05Z")

</div>

Hi Team,

When I request [https://api.atlassian.com/admin/v1/orgs](https://api.atlassian.com/admin/v1/orgs) this api I met “code”:“ADMIN-400-4”,“status”:“400”,“title”:“INVALID\_PARAM”,“detail”:“Organization: is not with the new user management experience” this error , and we are now the UI page is certralized user management, how can I fix it?

Thank you

---

<div class="post-metadata">

**Author:** ![Mihai\_leanzero](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/mihai_leanzero/32/55980_2.png) [@Mihai\_leanzero](https://community.developer.atlassian.com/u/Mihai_leanzero)\
**Post date:** [September 29, 2026, 11:00am UTC](https://community.developer.atlassian.com/t/how-can-i-check-the-error-organization-is-not-with-the-new-user-management-experience/102939/2 "2026-09-29T11:00:34Z")

</div>

Hi @yuanming,

I doubt it’s the bare list call. The /admin/v1/orgs list doesn’t document that error at all, and it works fine against a centralized org.

That exact error detail from your title is what the org-scoped user and directory calls return, like /v1/orgs/{orgId}/users/search. ADMIN-400-4 is generic. The detail string is what counts.

Is the failing request really the list, or a follow-up call built from its result, and does the key cover more than one org? There’s no API for which experience an org is on, only [admin.atlassian.com](http://admin.atlassian.com) \> your org \> Directory tab, where a Users page means centralized.