JIT Personas and Workflow

The JIT access workflow involves the participation of the following personas:

JIT Workflow

Diagram: the JIT workflow between the administrator, approvers, and requesters, the JIT Portal, integrations, cloud providers, and identity providers

  1. An administrator adds an eligibility, which is a predefined policy that states who can request access and what they can request (account scope/permissions/duration). The policy also defines whether access is approved and granted automatically, or whether it must wait for an explicit approval.
  2. A requester, who has been included in an eligibility, requests access to an account. The user’s ability to request access is based on the eligibility criteria defined by the administrator.
  3. If the eligibility criteria stipulates automatic approval, the access request is approved and granted immediately.
  4. If the eligibility criteria requires explicit approval, the request is pending, and an email notification/Slack/Teams message (if enabled) is sent to the approvers. Optionally, you can also define additional email addresses or Slack/Teams channels to receive notifications.
  5. An approver reviews the request, and decides whether to approve or deny.
  6. When an approver approves the request:
    • The requester is granted access to the account for a specific period of time using the defined permission level. If there are multiple approvers on the same level in the approval workflow, only one of them needs to grant approval.
    • If you configured a multi-level approval workflow, a notification is sent to the second- or third-level approver for review. Access is only granted to the requester after the final approver defined in the eligibility approves the request.
  7. After the duration of the entitlement has expired, the requester’s access is automatically revoked.