We have now deprecated and will be removing the is_admin response field from the Users API to accommodate global user management.

The change is related to the Improvements to PermissionSets API and Users API and the Removal of fields from Users API announcements.

What is changing?

We have deprecated the is_admin response field from six endpoints of the Users API, including:

• GET /users
• GET /users/find
• GET /users/me
• GET /users/{id}
• POST /users
• PUT /users/{id}

The response field will be removed in a year - on August 9, 2023.

As mentioned in the Improvements to PermissionSets API and Users API announcement, we have added a new access response field to Users API. We recommend using the access field instead, as it includes information about the user’s admin status, the permission sets assigned to the user and the permission set IDs.

Why is it changing?

The is_admin response field describes whether the user is an admin, but does not contain information about the user’s permission sets. In order to take full advantage of the new app-specific user access model, the access response field has been implemented and should be used instead.

Who will be affected?

Everyone who is using the is_admin response field to determine whether the user is an admin.

Let us know in the Developer’s Community if you have any questions or comments.