Update a custom role
Authentication
An auth_token should be provided to authenticate a session.
To obtain an auth_token, see the /api/v1/authenticate POST request.
Path parameters
Workspace identifier.
Either a positive integer organization ID, or the literal string my to target the caller’s own Workspace.
Request
New unique role name within the Workspace.
Use letters, digits, spaces, dashes, underscores, ampersands, and apostrophes.
Leading and trailing whitespace is trimmed before validation and storage.
Omit the field to leave the name unchanged, because an explicit null is rejected.
Free-text description of the role.
Pass null to clear it, which stores an empty string.
When provided, it must be 2 to 250 characters.
Leading and trailing whitespace is trimmed before validation and storage.
When provided, replaces the existing permission list.
Mutually exclusive with permissions.
Deprecated or deleted permissions are rejected.
Omit the field to leave assignments unchanged, and send [] to clear them, because an explicit null is rejected.
Resource and action pairs replacing the existing permission list, resolved to permission IDs on the server.
Mutually exclusive with permission_ids.
Deprecated or deleted permissions are rejected.
Omit the field to leave assignments unchanged, and send [] to clear them, because an explicit null is rejected.
Response
Human-readable description of the role. An empty string when no description has been set.
Whether this is a system-defined role or an organization’s custom role.
True for built-in system roles, which can’t be modified or deleted.