Create a custom role

POST 
/api/v1/organizations/current/roles

Create a least-privilege custom role. Admin/owner only.

Admission-gated behind release_custom_roles (404 when off). Permissions must be concrete scopes from the catalogue and a subset of what the creator can grant (reduce-only, mirrors API-key scope composition).

Request

Responses

201

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.