📣 The Voice of 200 CISOs: where identity programs break.

Just-in-time access

Access that is asked for, approved, and expires on its own.

Oak turns standing privilege into time-bound access: requested where your people already work, approved with full context, and removed when the window closes.

Book a demo →
StandingEligibleLivePlatform Engineering · AWS production
OAK FOUNDDONE

6 people hold standing admin on AWS production. None of it has an end date.

Done. 6 standing admin grants are now eligible: requested in Slack, approved by a manager, expiring after 8 hours at most. Logged.

What we hear

Admin gets granted for good. Nobody takes it back.

The 2am shortcut

An engineer needs production admin at 2am to fix an incident. It gets granted for good, because granting it for two hours was never practical.

Approvers can't tell

Whoever is doing the approval for access oftentimes lacks that context of, does this person truly need this?

Identity strategy, telecom

It never comes back

Three years ago, they needed to give themselves owner. Three years later, they still have it.

IT services leader

What changes

Not permanent by default. Eligible by design.

Every grant carries its own end. Standing permissions become eligibility, so privileged access stops piling up and trends to zero for every app Oak governs. Drag to compare.

Standing
Oak

Zero standing privilege for the access Oak governs.

Decide · Ask · Approve · Expire

From standing admin to access with an end date.

01

Decide who can ask

One eligibility rule sets who may ask, for what, for how long and who approves. People match by attribute from Oak's live identity graph, never by a list of names, so a reorg never breaks the rule. Test every rule before it goes live.

02

Ask where the work is

Requests start in Slack or in Oak. People see only what they're eligible for, give a reason and submit in under a minute, without leaving the incident.

03

Approve with the full request in view

The requester's manager, the app owner or a group decides, up to three levels, or the rule approves routine requests on its own. No one approves their own request, and one decline ends it.

04

Expire on its own

Access is removed when the window closes, from one minute to 24 hours. It can be handed back early or extended. Every request, decision, grant and removal is recorded with actor and reason, ready to export.

Eligibility ruleEngineering · India
Who can askDepartment is Engineering · Location is IndiaAccessAWS · prod-adminLongest window8 hoursApproverRequester's managerReasonRequiredCovers42 people, liveStatusTested · Ready to enable
Matched by attribute, not by name
#platform-oncallSlack

/oak request

O

Oak APP

Tom Ortiz requests AWS prod-admin for 4 hours

Reason: INC-4471 · Eligible through Engineering · India

Submit request

✓ Sent to Maya Chen for approval.

Access request

Tom Ortiz · AWS prod-admin · 4 hours

TeamPlatform EngineeringRuleEngineering · India, up to 8 hoursReasonINC-4471ApproverMaya Chen, manager
Approve for 4hDeny

✓ Approved by Maya Chen in Slack. Expires at 18:30. Logged.

Live grantsToday
RequesterAccessWindowStatus
Tom OrtizAWS · prod-admin14:30 to 18:30Live · 2h 41m left
Priya NairOkta · Salesforce admin09:00 to 11:00Expired · removed
Lee Kim1Password · Finance vault10:15 to 12:15Handed back early
Dan RossAWS · billing-admin1 hourDeclined
Every request, decision, grant and removal on recordExport

See it in your estate

See who holds standing admin, and make it eligible.

Bring one app. We'll show you its standing privilege, write an eligibility rule with you, and run a live request in Slack.

Book a demo →

Why Oak

Built to govern. Not just to watch.

One graph, every identity

Agents sit next to the people and service accounts behind them, so you see the identity an agent borrows and its real reach.

Activity, not assumptions

No one else has an activity-based identity graph. Not only who has access, but who should.

Not just a timer

A time limit on a broad grant is still a broad grant. Oak narrows what is granted, not only for how long, and ties every grant to the Jira ticket or Slack message behind it.

Your team approves every change

Oak's agents do the work. Every action is explained, approved, reversible and on record.

“I don’t think you are just an AI agent visibility company. You’re talking about a complete purview of everything.”

IAM leader, automotive retail

Connects anything

Your apps already connect to Oak. JIT runs on them.

Just-in-time access runs on the connector already in place: no agent on your infrastructure, no rebuilt apps. Through Okta, it reaches every app behind your IdP.

And hundreds more, with new connectors built in days.

Start with just-in-time. Keep going.

The same graph governs everything else.

The graph that decides who can ask also right-sizes access, mines your roles and governs your agents.

Questions, answered.

We already have JIT in our PAM or cloud provider. Why Oak?

Oak doesn't replace your vault. It brings eligibility to the apps your vault doesn't cover, including every app behind Okta, and decides it from the same identity graph that runs your reviews and roles.

Will this slow down engineers on call?

No. Asking takes under a minute, from Slack, without leaving the incident. Routine requests can be approved by the rule itself, so only sensitive access waits for a person.

Who approves, and can people approve their own access?

The requester's manager, the app owner or a group, up to three levels, or your own approval system. No one approves their own request, and one decline ends it.

How long does access last?

As long as the rule allows, from one minute to 24 hours. When the window closes, access is removed with nothing left to clean up. People can hand it back early, or ask to extend.

Does it cover AI agents?

Yes. The same rules cover agents and the tools they call, with the owner as the ceiling: an agent never gets more than the person it acts for.

Access with an end date. Make it the default.

See a rule, a request and a live grant in one session.

Book a demo →