Start an access review.
curl --request POST \ --url https://auth.example.com/api/admin/compliance/access-reviews \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "name": "Quarterly privileged access review", "description": "Review all tenant admins.", "scope": "role", "scope_value": "admin", "due_date": "2026-07-31" }'Starts a review of who has some access, taking its items from every store the tenant’s accounts live in: users with a role (role), members of an organization (organization), all active registered users (all_users), or those not signed in for inactive_days (default 90; inactive_users, by the sign-in their sessions recorded). A review over 1000 items is refused (access_review_too_large), and an inactive-user review that needs more than 5000 sign-in lookups too (access_review_scan_limit); narrow the scope.
Authorizations
Section titled “Authorizations ”Request Body required
Section titled “Request Body required ”object
The role id (role) or organization id (organization); required for them.
A date (the end of that day, UTC) or a date-time.
For inactive_users; default 90.
Example
{ "name": "Quarterly privileged access review", "description": "Review all tenant admins.", "scope": "role", "scope_value": "admin", "due_date": "2026-07-31"}Responses
Section titled “ Responses ”Compliance access review creation response.
object
object
Example
{ "scope": "all_users", "status": "pending"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}