Skip to content

Agent Insights — standing instructions and autonomous remediation

Most of AtmanID is pull-based: you open a dashboard, ask Iris a question, or wait for a scheduled report. Agent Insights is the push-based counterpart — a standing subscription that watches for a condition you care about and tells you the moment it happens, without you having to go looking.

It ships in two layers, and they’re deliberately separate:

  1. Notifications — “tell me when X happens.” Always available, always just a notification. Nothing is changed on your behalf.
  2. Autonomous remediation — an optional, narrowly-scoped, separately-granted permission for the agent to fix one specific kind of finding automatically, instead of only notifying you about it.

Setting up a standing instruction

Go to Settings → My Agent and open the Standing Instructions card. You can subscribe to three event types:

Event type Fires when
SoD violation A new Separation-of-Duties violation is detected
Certification failure A certification review decided to revoke access, and that access is still active past its grace period
High risk score A user’s composite risk score crosses a threshold — a default from the settings toggle, or the cutoff you set when you subscribe through Iris

Subscriptions are evaluated on an hourly sweep. When one matches, you get an in-app notification, and the match is written to the audit trail attributed to you personally — not to a generic system job — so the record of “why was I told this” stays intact.

You don’t have to use the settings page. You can ask Iris directly:

“Tell me about SoD violations in Finance.”

Iris scopes the subscription to the Finance department and creates it the same way the settings toggle does — same underlying subscription, same audit trail, just a different way of expressing it. (Department scoping is currently available for SoD violations; certification-failure and risk-score subscriptions already take their own thresholds, like a grace-period window or a risk cutoff.) You can also ask Iris what you’re currently subscribed to, and it will read your standing instructions back to you.

A creation or edit made conversationally goes through the same confirmation step every Iris-initiated change does — see Iris explained for how that confirmation gate works. Once you’ve confirmed it once, you can authorize Iris to make that specific kind of change without asking again next time, the same standing-authorization mechanism available to any other Iris write action.

Autonomous remediation — the narrow exception

Notifications never change anything. Autonomous remediation is different: it lets the agent take an action on your behalf, without a per-instance confirmation click, when a subscription’s condition matches.

This is deliberately restricted to exactly one pattern today: a certification review already decided to revoke an entitlement, and the revoke didn’t take — the access is still active past its grace period. That’s the narrowest case available, because the judgment call (“should this access be removed?”) was already made by a human during the certification review. Turning on autonomous remediation for this pattern just means the agent closes the fulfillment gap instead of you having to notice the notification and manually re-trigger the revoke.

SoD violations and risk-score crossings are not eligible for autonomous remediation — both require a human judgment call about which specific access to remove, not a single unambiguous action, so those stay notify-only.

Turning it on requires a separate, explicit step from the notification subscription itself: a “Confirm & enable” grant on that specific subscription, distinct from just having notifications turned on. It’s revocable at any time — turning it back off reverts that subscription to notify-only immediately, with no partial or delayed state.

When the agent does act autonomously, the audit trail marks it distinctly: you can tell an autonomous remediation apart from an action you clicked to confirm yourself, and both are distinct from a plain notification. Autonomous remediation also passes through the same delegation and risk checks as any other agent-executed write — it doesn’t get a separate, looser path just because no one clicked a button.

What this is (and isn’t)

Agent Insights is not a general-purpose automation engine. It’s scoped, auditable, and — outside the one remediation pattern above — strictly observational. If you’re looking for tenant-wide, admin-configured automation across many users at once, that’s a different capability (Playbooks, configured by an administrator); Agent Insights is your own personal standing instruction over your own subscriptions, not a policy that applies to anyone else.

© AtmanID · Privacy