In addition to role-based privileges, you can assign or deny privileges directly to individual users. This is useful when a user needs a specific permission that is not covered by their roles, or when you need to block access to a privilege that their role would otherwise grant. Direct denies override any role-based grants during privilege evaluation — a deny on a user will always win regardless of what roles the user belongs to.Documentation Index
Fetch the complete documentation index at: https://alphabet-06152314.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Admin endpoints
The following endpoints require the PrivilegeManagers authorization policy.Assign a direct privilege to a user
effect field to control whether the assignment grants or blocks the privilege.
Path parameters
The ID of the user to assign the privilege to.
Request body
The ID of the privilege to assign.
The effect of this assignment. Accepted values:
Allow— explicitly grants the privilege to this user, in addition to any role-based grants.Deny— explicitly blocks the privilege for this user, overriding any role-based grants.
Optional expiration timestamp. When omitted, the assignment does not expire.
Free-text justification for the assignment. Stored with the audit record.
Responses
200 OK
The assignment was created successfully.
Example — assigning a deny
Get effective privileges for a user
Path parameters
The ID of the user to evaluate.
Response — 200 OK
Example
Revoke a direct privilege from a user
Revoking a direct assignment removes it from evaluation but preserves the full audit trail. The historical record of the assignment is not deleted.
Path parameters
The ID of the user.
The ID of the privilege assignment to revoke.
Responses
200 OK
The assignment was revoked successfully.
The revocation failed, for example because no matching assignment exists.
Get privilege audit history for a user
Path parameters
The ID of the user to retrieve audit history for.
Query parameters
Maximum number of audit records to return. Values below 1 are coerced to 100.
Number of records to skip for pagination. Values below 0 are coerced to 0.
Response — 200 OK
Assign a policy directly to a user
Path parameters
The ID of the user to assign the policy to.
Request body
The ID of the composite privilege policy to assign.
Optional expiration timestamp for this policy assignment.
Responses
200 OK
The policy was assigned to the user successfully.
The assignment failed, for example because the policy ID is invalid.
Self-service endpoints
The following endpoints require only an authenticated user (Bearer token). No elevated policy is needed.Get your own effective privileges
Response — 200 OK
Same structure as the admin effective privileges response. See Get effective privileges for a user above.
Request temporary privilege access
Request body
The ID of the privilege you are requesting.
Business justification for the access request. Required for audit purposes.
Number of days you need this privilege. The approver may grant a shorter duration.
Optional email address of a specific approver. When omitted, the request is routed through the default approval workflow.
Responses
The ID of the newly created privilege request. Use this ID to track approval status.
The request creation failed, for example because the privilege ID is invalid.