Skip to main content
Custom Access lets you make anything requestable, not just directly connected applications - an internal tool, an application not integrated with Oleria, or any action someone can perform. Custom Access items use the same justification, duration, and approval chain options as applications. The difference is how access gets provisioned once a request is approved: automatically through a webhook action you own, or through a manual action that notifies an admin to provision it themselves.
1

Open Custom Access

Go to Governance -> Access Requests -> Custom Access, select New custom access, and choose New webhook action or New manual action.
2

Name and describe it

Give the item a name and description. Employees see these in the request catalog.
3

Configure provisioning

Select the webhook that provisions this access, and add any parameters that should be sent on every request.
4

Configure the request form

Define the fields employees fill in when they request this access. Fields can be required or optional.New custom access page showing the provisioning webhook, its parameters, and the user fields that make up the request form
5

Set duration, expiration, and justification

Choose whether access is permanent or time-limited, how long a pending request can stay open before it expires, and whether a business justification is required. For a manual action, this expiration also limits how long an admin has to complete the request before it fails.
6

Assign an approval chain

Select the approval chain that should govern requests for this item, and choose whether to notify approvers by email or Slack.
A webhook action is provisioned and revoked automatically. If the webhook doesn’t return a successful response, the request or revocation fails without affecting other pending requests.A manual action is provisioned and revoked by an admin. Once a request is approved, Oleria notifies your workspace admins, and the request shows Pending manual action until an admin completes it, fails it, or it expires.

​
Requesting Custom Access

Employees request Custom Access the same way they request application access, from the Custom Access tab in the Governance App catalog. The request form shows whatever fields you’ve configured instead of an application and role, and submissions are tracked separately under My Custom Access Requests. For a manual action, the requester sees Pending manual action while it waits on an admin - the runbook itself is never shown to them.
Request access dialog for a custom access item, showing the configured customer and role fields, the requested duration, and peer group access

​
Completing a manual action

When a manual action’s request is approved, Oleria notifies your workspace admins with the request details and the provisioning runbook. An admin can then, from that notification or from the request in Oleria:
  • Mark complete, once they’ve provisioned access by following the runbook. An admin-facing note and an evidence URL are both optional. The request moves to Manually provisioned.
  • Mark failed, if they can’t provision access. A reason is required. The request moves to Failed.
Revocation works the same way: when access needs to be removed, your workspace admins are notified with the revoke runbook, and the request shows Pending manual revoke until an admin marks it complete (with the same optional note and evidence URL) or failed (with a required reason). The note or reason, and any evidence URL, are captured on the request for audit.
If a manual action isn’t completed before the request expires, it fails automatically the same way an unanswered webhook does.

​
Contact us

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