Skip to main content
Provide just-in-time access to applications for employees. Every request runs through an approval chain that you define, and Oleria grants or revokes the access automatically once a decision is made.

How access requests work

  1. Admins configure request sources - as an administrator, you choose what employees can request from SSO applications, integrated applications, and Custom Access, then assign an approval chain to each level of access.
  2. Employees submit requests - employees browse the catalog of requestable access and submit a request with a justification.
  3. Approvers get notified - Oleria notifies approvers by email, Slack, or Microsoft Teams as each step in the chain activates.
  4. Approvers decide - approvers approve or deny the request, or a step resolves automatically based on the approval method you configured.
  5. Oleria grants or denies access - once every step in the chain is approved, Oleria provisions the access. A denial at any step stops the chain and denies the request.

Configure what employees can request

Each request source, and the approvals it runs through, is configured on its own page.

Approval chains

The sequence of approvals a request must clear before access is granted. See Approval Chains.

SSO applications

Applications your identity provider federates, granted through an IdP group. See SSO Applications.

Integrated applications

Applications connected directly to Oleria, granted as a group or a role in the application itself. See Integrated Applications.

Custom Access

Anything else you want to make requestable, provisioned automatically by a webhook you own or manually by an admin you designate. See Custom Access.

Reviewing and approving requests

Approvers review and act on requests from Approvals in the Governance App, under the Pending, Approved, and Denied tabs. Selecting a request shows the application, role, requested duration, business justification, and the approval history for the chain so far. Approvers can:
  • Approve the request.
  • Deny the request, which requires a reason.
Notifications sent by email, Slack, or Teams include the same Approve and Deny actions, so approvers can act without opening the Governance App.

Request statuses

Admin overrides

Administrators can override a request’s outcome directly - approving, denying, or revoking access outside the normal chain. Every override requires a reason, and it’s recorded in the request’s activity history alongside the decisions made by the chain.
Only Oleria Administrators can configure request sources, build approval chains, or override request decisions. View role permissions.

Contact us

For questions, contact us at support@oleria.com.