Set a member's roles in an organization
Replace a member’s roles in an organization with the roles given, and return the member. The
member’s current sessions must reauthorize, so the new roles apply immediately. The member
may still be INVITED. The organization and the member are identified by the path
parameters alone. The x-hh-org-id header does not participate.
Each role must be one the organization’s roles manifest defines for organizations, which are the roles the HoneyHive app offers there. Any other role is refused with 400, including one a manifest change removed, so writing back roles read before such a change can fail. When the organization has no valid roles manifest in force, the roles cannot be checked and the request is refused with 409.
When an API key makes the request, it cannot take the ability to revoke API keys from a
member who has signed in. If the member’s roles grant org.roles.get, org.roles.set,
org.fine_grained_api_key_cp.list and org.fine_grained_api_key_cp.delete, and the new
roles would not, the request is refused with 409 and the change has to be made in the
HoneyHive app. An API key can still give any member those roles, and can change the roles of
a member who has not signed in yet.
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.
Authorizations
Path Parameters
Body
The member's new roles at this scope, replacing the old ones. Each must be a role the organization's roles manifest defines for this scope's type, which are the roles the HoneyHive app offers for a member here. Any other role is refused with 400, including one a manifest change removed, so writing back roles read before a manifest change can fail
11