Remove someone from an organization
Remove a user from an organization and from every virtual data plane, workspace and project
in it, which also withdraws a pending invite. The user’s current sessions must reauthorize.
Their HoneyHive user stays, along with their memberships of other organizations. The
organization and the user are identified by the path parameters alone. The x-hh-org-id
header does not participate.
When an API key makes the request, it cannot remove a member who has signed in and whose
roles grant org.roles.get, org.roles.set, org.fine_grained_api_key_cp.list and
org.fine_grained_api_key_cp.delete, so someone in the organization can always revoke the
key. Such a request is refused with 409, and the member has to be removed in the HoneyHive
app. A member who has not signed in yet can be removed with an API key whatever their roles.
When the organization has no valid roles manifest in force, a member who has signed in
cannot be checked, and an API key’s request to remove them is refused with 409.
Available on self-hosted deployments that do not enable an SSO group scheme. Elsewhere this operation returns 404. An API key that carries a membership permission can carry no permission other than the roles and membership permissions, and is created on an organization.