Incidents
The two lists that tell you what needs a decision — ungoverned assets and flagged sessions.
console.superalign.ai/incidents
An incident is something we found that nobody has decided about yet. The console collects them in the Incidents section, the first section in the left menu, in two pages:
- Open — everything waiting for a decision.
- Resolved — everything someone has decided, with who and when.
Two kinds of incident
The Assets and Sessions tabs split the list by where the incident came from.
| Kind | An incident is | Open means | Resolved means |
|---|---|---|---|
| Asset | One AI asset, once across the fleet | Nobody has taken an action on it yet | Someone applied Allow, Warn, or Block |
| Session | One recorded conversation that broke a Session Policy | Nobody has saved an outcome yet | Someone saved an outcome for it |
Reading the list
The Group by menu on the Open page changes how the list is laid out:
- Incident — each asset or session on its own.
- Policy — incidents grouped under the policy that raised them, so you can clear a whole kind of problem at once.
Asset incidents sort highest risk first and carry the Risk, Asset Name, Status, Asset Type, Instances, and Detected columns. Session incidents carry Severity, Session, User, Tags, Enforcement, Messages, and Last Activity — the Enforcement column shows what the session policy did on the endpoint (see On-device enforcement). On the Resolved page, an Outcome column shows how each session incident was closed.
Filter asset incidents by risk level and asset type, and session incidents by the usual session filters. Insights deep-links here: the Govern button opens the asset incidents filtered to one risk level.
The ticket
Click a row and the incident opens as a ticket, with the list narrowing beside it. J and K (or the arrow keys) step to the next and previous incident, and Esc closes. An asset incident’s ticket shows the asset’s graph and its Failed Policies. A session incident’s ticket shows the Session Trace details, with a Resolution section on the Resolved page naming the outcome, who set it, and when.
Who sees what
Admins and Owners resolve incidents. Auditors see the lists but cannot resolve. Members never see the Incidents section.
Next steps
- Resolve incidents for the asset actions and session outcomes
- On-device enforcement for what the endpoint does with each action