Elevate is just-in-time privilege escalation for your team: "Request, approve, and audit just-in-time access." Instead of leaving people permanently in a powerful role, they request that role when they need it, for as long as they need it, with a reason attached.

The rail has four tabs: Access, Approvals, Grants, and Policy.
Access
"Request temporary access" — "Access expires automatically. Reason is retained in audit history."
| Field | Details |
|---|---|
| Target type | What you are elevating into, for example Environment role. |
| Duration | How long the grant lasts (default: 30 minutes), capped by the environment policy. |
| Role | The role to assume. |
| Reason | Why this access is needed. Retained in audit history. |
| Ticket reference | Optional link to the incident or ticket, for example INC-1234. |
Click "Request access" to submit. My requests below tracks your own submissions with Target, Status, Duration, and Expires.
Approvals
"Approval queue" — the requests waiting on a decision, with Requester, Target, Reason, and Duration.
One rule is enforced by the server, not by convention: "Requester cannot approve their own request." Even an admin who could otherwise approve anything must have someone else sign off on their own escalation.
Grants
"Access grants" — active and past grants, with Grantee, Target, Status, and Window.
The important behaviour is noted on the page: "Runtime authorization checks expiry synchronously." Expiry is not a background sweep — the moment the window closes, the next authorization check fails. There is no gap where a stale grant still works.
Policy
"Environment policy" — the rules the server snapshots onto each request. Because the policy is captured at request time, tightening it later does not retroactively change grants already in flight.
| Setting | Effect |
|---|---|
| Require administrator approval | An admin must approve requests before they become grants. |
| Require recent MFA or TOTP activation code | The requester must prove a recent MFA or TOTP challenge. |
| Maximum duration (minutes) | Caps how long any single grant can last. |
Click "Save policy" to apply.
Elevate vs impersonation
The two look similar and solve different problems:
| Elevates | Configured in | |
|---|---|---|
| Elevate | A team member's own privileges within an environment. | This page. |
| Impersonation | A team member's ability to act as an end user. | Users > Escalation. |
Both are fully audited. Elevate emits the ELEVATE_ACCESS_* event family — requested, approved, denied, cancelled, activated, revoked, expired — and impersonation emits USER_IMPERSONATION_*. Both appear under the Administration category in Audit > Event Types.
Related
| Read | To learn how to |
|---|---|
| Authorization | Define the roles Elevate grants |
| Users | Grant time-boxed impersonation of an end user |
| Audit | Review the full escalation trail |
| Tenants | Manage who is on the team in the first place |