Governance
Cross-app
GRC Lead

Surface dormant access automatically with last activity in days on every review line, not just at campaign time

Summary: 95% of enterprise permissions go unused — yet most organizations discover dormant access only through quarterly reports assembled by hand from a dozen admin consoles. Oleria Trustfusion, an AI-native identity security platform, eliminates the dormant access detection scramble by computing usage continuously and surfacing last-activity in days on every review line, so reviewers see dormant access where the decision happens — not in a separate report nobody reads.

Outcome

Surface dormant access automatically, with last activity in days on every line.

Find dormant access before audit catches you. Continuous, usage-aware, no separate dormancy report to assemble.‌

Why this is hard without Oleria

95% of enterprise permissions go unused (Microsoft Security). The standard answer is the dormancy report — generated quarterly from a dozen admin consoles, manually correlated, attached to a ticket. By the time the report runs, the data is stale; by the time it's reviewed, six more months of dormancy have accumulated.

Most identity tools treat dormancy as a separate report, run once a quarter, parsed by hand. The signal exists in the data; it just isn't surfaced where the decision happens. Reviewers approve dormant access because they don't see that it's dormant.

What Oleria delivers

Oleria shows dormant days per line in every review so reviewers revoke unused access at the moment of the certification decision.

Per-line dormant days

Every line in every review shows last-activity in days. The signal lives where the decision happens.

Customizable thresholds

Default 90-day threshold across access reviews. Admins customize per organization and per feature.

Continuous evaluation

Dormancy is computed continuously, not reported quarterly. Dormant access flags surface in every access review automatically.

Bulk-revoke for over-threshold

When dormancy is clear, revocation is one action. Reviewer accepts the recommendation and moves on.

Outcomes at a glance

Per-line, in days
Dormancy signal
90-day default, customizable
Threshold
Per-org, per-feature, per-app
Granularity

Oleria AI

Oleria's AI surfaces dormant days alongside every reviewable access line. Past the threshold, the AI's recommendation is "Reject." Reviewer confirms; access narrows continuously, not just at audit time.

How it works

  1. Connect apps — Oleria pulls login and activity events from every connected app.
  2. Dormancy computed continuously — Per identity, per access line, per day.
  3. Surfaced inline — Every review shows last-activity per line.
  4. Action options — Approve with a justification (captured in audit), or revoke with one click.

What good looks like

Time to identify dormant access Days → continuous

Quarterly dormancy reports Eliminated

95% unused permissions stat Materially reduced over time

Audit findings on dormant access Eliminated

Find out how much dormant access your organization is carrying today.

If 95% of enterprise permissions go unused, the question is how much of that is in your environment — and what it's costing in both risk and compliance exposure. Oleria's Identity Security Maturity Assessment benchmarks your current dormant access posture.

Frequently Asked Questions

Does dormancy work for non-human identities and AI agents?

Yes — API patterns, scheduled jobs, and action streams apply the same dormancy logic.

How is this different from IdP dormancy reports?

Oleria correlates IdP authentication with app-level activity — per-permission, not per-identity.

What about access that's needed but rarely used?

Reviewers override per line with documented justification logged in the audit trail.

What's the default threshold and why?

90 days — matches common quarterly review cadence and seasonal use patterns.

What does dormancy actually measure?

Days since last login or last access activity for a specific permission in the connected app.