Removing a user can be critical in several scenarios:

Some users may no longer require access to a group due to changes in roles and responsibilities within your organization.
Removing users who no longer belong to a group or organization helps secure sensitive information and maintain data integrity.
You may have limited seats in your organization and want to reallocate them to new team members or other users.

Requirements

"Platform management: Groups" permission

📘
Note Starting August 13, 2024, you can no longer remove users from an organization via the web app, but this endpoint remains available as an alternative. If a user is removed from their only organization, a new SafetyCulture organization will be created for them, with access limited to that user. To prevent this, you can set the user as inactive using the Update a user endpoint.

Removing a user from a group will revoke access, but their past contributions, such as completed inspections, remain part of the group's records. If you remove a user from your organization, the templates and inspections that user owns will be reassigned to you by default. However, you can specify who you want to reassign them to by adding the replacement_user parameter to your request.

🚧
You cannot remove yourself from groups or organizations. In addition, a user cannot be removed if they are the only remaining user with the default "Administrator" permission set in the organization.