Role mining
Roles built on your org and how people actually work.
Pick an app and Oak proposes a smaller, usage-backed role and group model built on your org structure that is continuously updated.
Book a demo →41 groups for 38 people. 3 roles cover everything they actually use.
Proposal ready. 41 groups become 3 roles, and nobody loses access they use. Waiting for your approval.
What we hear
Thousands of groups. Nobody can explain them.
Groups60,000
People85,000
Roles exploded
We have roughly 60,000 groups, even though we only have 85,000 people.
Identity engineering, technology
New hire“same as Joe”
23 groups inherited4 used
Access gets copied, never cleaned
New hires get access “same as Joe”. Legacy groups stay, because removing them might break something.
Role projectSigned off once
Org changesevery week
The model drifts the day it ends
Role mining, or role engineering, it's always a continuous process.
IAM leader, payments
What changes
Not roles from a workshop. Roles from how you work.
Oak reads three signals together: your org structure, every entitlement and what each person actually uses. Then it finds the smallest model that keeps everyone's used access. Drag to compare.
access anyone actually uses is lost when the model is restructured.
to a proposed model, not a role project that runs for years.
simpler role and group structure, in a single pass.
Based on live customer environments in large enterprises.
Pick · Review · Approve · Stay current
Three signals in. A smaller model out.
01
Pick an app
Oak shows where mining helps most. Pick one app, choose how far to go (Aggressive, Balanced or Conservative) and how far back to look: 30, 90 or 180 days.
02
Review the proposal
See today next to proposed, with the reason behind each change. Oak starts from your departments, teams and titles, then refines with entitlements and real use, so every role is one a manager can read and approve.
03
Approve and execute
Approve the model as one campaign. Changes run through the ServiceNow or Jira you already use, and a task counts as done only when Oak sees the change in the app.
04
Stay current
The model refreshes as people join, move and leave, so roles don't drift back. The same model scopes your access reviews, so reviewers certify fewer, meaningful items.
| App | Groups | Where mining helps |
|---|---|---|
| Salesforce | 412 | High |
| GitHub | 286 | High |
| Microsoft Entra ID | 1,940 | Medium |
| Snowflake | 64 | Low |
| Measure | Today | Proposed |
|---|---|---|
| Groups and roles | 41 | 3 |
| Grants | 214 | 31 |
| Critical grants | 12 | 4 |
| Used access lost | — | 0 |
Why is fin-ops-legacy-02 going away? Nobody used it in 90 days. The Finance analyst role covers the rest.
Removed from the proposal. Nobody loses access they use.
| Role | Change | People | Status |
|---|---|---|---|
| Finance analyst | No drift | 24 | In sync |
| Finance approver | 2 unused | 9 | Re-mined |
| Sales ops manager | Mover | 5 | Flagged |
See it in your estate
Bring one app. See the groups nobody needs.
We'll show you its unused access, the groups that overlap and the smaller model hiding in it.
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.
A timerprod-admin · 8 hours
OakNetSuite · Create bills
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
Keep your IdP, IGA and ticketing. Oak works with them.
Oak mines app by app through the connectors already in place, and runs changes through the ServiceNow or Jira you already use.
And hundreds more, from Okta and Active Directory to SAP, with new connectors built in days.
Start with roles. Keep going.
The same model governs everything else.
The roles Oak mines also scope your access reviews and keep least privilege from drifting.
Questions, answered.
Our IGA already has role mining. Why Oak?
Most role mining clusters on entitlements and adds roles on top. Oak starts from your org structure, refines with entitlements and real use, and removes structure instead of adding it. It keeps running, so the model doesn't drift after go-live.
Will anyone lose access they need?
No one loses access they used in the lookback period you choose: 30, 90 or 180 days. Restructuring changes no one's effective access, and any access added to simplify a group never raises anyone's privilege level.
Does AI decide what changes?
No. A deterministic engine finds the model, and AI explains each recommendation in plain language. Nothing changes until your team approves, and every campaign is on record for audit.
Do we need to replace our IdP or IGA?
No. Oak works app by app through the connectors already in place, alongside the IdP, IGA and ticketing you run today.
How does role mining connect to just-in-time access and lifecycle?
It's the same model. It scopes your access reviews, sets which access stays standing and which is granted just in time, and generates joiner, mover and leaver policies.
Start with one app. See the model in minutes.
Built on your org, approved by your team, and kept true as you change.
Book a demo →