Incident settings
Incident settings is under Workspace in the sidebar. It has three cards: Automatic incidents, Learned dismissals and Correlation groups.
Only admins can open this page. A member or viewer who opens it sees a 403 page with the text “Forbidden: only workspace admins can manage correlation groups.”
For what incidents are and how to work them, see Incidents.
Automatic incidents
Section titled “Automatic incidents”The card description reads: “The engine that correlates events into incidents, with one switch per detector. Switching a detector off stops its checks for this workspace entirely.”
The entitlement line
Section titled “The entitlement line”The first line on the card tells you why the workspace has, or does not have, the feature.
| Line | Meaning |
|---|---|
| “Included in your plan.” | The workspace is on Super |
| “Provided by the Automated Identity Incidents add-on.” | The workspace is on Pro or Max with the add-on |
| “Automated Identity Incidents is included in Super and available as an add-on on Pro and Max.” | The workspace is not entitled |
See Plans and billing.
The master switch
Section titled “The master switch”The checkbox Enable automatic incidents for this workspace is the master switch.
| State | Text under the checkbox | Effect |
|---|---|---|
| Ticked | “Events are correlated as they arrive; the detectors below decide what opens an incident.” | Incidents are on |
| Not ticked | “Off: events are stored and classified, but nothing is correlated and no detector runs.” | Incidents are off |
| Not entitled | “Not available on the current plan.” with the link Manage plan | Every control on the card is disabled. Manage plan opens Billing. |
When the master switch is off:
- The Incidents row is hidden from the sidebar.
- The Needs attention strip is hidden from the dashboard.
- The incidents pages show Automatic incidents are switched off.
Detector switches
Section titled “Detector switches”Below the master switch are two groups of checkboxes: Workforce detectors and Customer detectors. Each detector has a title and a description. The four detectors that work across platforms are listed under Workforce detectors.
- A ticked detector is on. Untick it to switch it off.
- Both groups are disabled while the master switch is off.
- A detector that is switched off does no checks for this workspace.
The footer reads “All detectors on.” or, for example, “2 detectors switched off.”
Choose Save detectors to save. Nothing on this card is saved until you do. You see the message “Detectors saved”.
Prefer a silence rule to switching a detector off. A silence rule applies to one pattern on one tenant and expires on its own. A switched-off detector stops for the whole workspace.
Learned dismissals
Section titled “Learned dismissals”The card description reads: “After three false-positive closes of the same pattern on one tenant inside 30 days, or one close with Silence ticked, matching incidents open on the Silenced tab instead of the Open tab. A rule expires 90 days after it last matched, and breaks out on its own when an incident grows past what it learned.”
The card also notes: “Only incidents are silenced. Event alerts (email, Teams and other channels) are not affected and still send for every event.”
A silenced incident still opens, still collects evidence and can still escalate. It is listed on the Silenced tab, not on Open. See Silenced incidents.
Learn from false-positive closes
Section titled “Learn from false-positive closes”The checkbox Learn from false-positive closes is on by default. It saves at once. There is no save button.
| State | Text under the checkbox | Message when you change it |
|---|---|---|
| Ticked | “On: false-positive closes teach silence rules, and armed rules silence matching incidents.” | “Learned dismissal on” |
| Not ticked | “Off: nothing new is learned and no new incident is silenced. Rules are kept for when it is switched back on.” | “Learned dismissal off” |
The checkbox is disabled when the workspace is not entitled to automatic incidents.
The silence rules table
Section titled “The silence rules table”The Silence rules table lists every rule for the workspace. Armed rules come first, then expired rules, then disarmed rules. Inside each state, the rules with the most break-outs come first.
| Column | What it shows |
|---|---|
| Pattern | The rule description, for example “Okta user.session.start (Sign-in) opening on an identity in Okta production, up to WARN” |
| Tenant | The one tenant the rule applies to |
| Armed | How long ago the rule was armed, and how: “Silenced at close” (someone ticked the silence box) or “Learned from 3 closes” |
| Hits | How many incidents the rule has silenced |
| Break-outs | How many silenced incidents grew past the rule and returned to the normal lists |
| State | A badge and a line of detail. See the next table. |
| (no heading) | The Disarm button, on armed rules only |
| State badge | Detail line | Meaning |
|---|---|---|
| Armed | “Expires in N days” or “Expires today” | The rule is silencing matching incidents. The expiry moves forward each time the rule matches. |
| Expired | “Expired N days ago” or “Expired today” | The rule did not match for 90 days and no longer silences anything |
| Disarmed | “Disarmed by email (this was real)”, “(undone at close)” or “(in settings)” | A person stopped the rule, and how they did it |
A rule with many break-outs is too broad for the activity on that tenant. Consider disarming it.
Disarm a rule
Section titled “Disarm a rule”- On the rule’s row, choose Disarm.
- The dialog Disarm this rule? names the rule and explains that it “stops silencing incidents, and the ones it is silencing now go back to the normal lists.”
- Choose Disarm rule.
You see the message “Rule disarmed. Incidents it was silencing are back in the normal lists.”
The rule is not deleted. It stays in the table with the state Disarmed.
Other ways a rule is disarmed
Section titled “Other ways a rule is disarmed”- A member or admin chooses This was real on a silenced incident.
- A member or admin chooses Undo on the message shown when the rule is armed.
The email to admins
Section titled “The email to admins”When a rule is armed, every workspace admin receives an email. The subject is “Identiguard is now silencing an incident pattern on tenant”. The heading is “Incidents are being silenced”. The button Review in Incident settings opens this page.
Correlation groups
Section titled “Correlation groups”The card description reads: “Tenants in the same group correlate with each other. Isolated is the default, and it keeps a tenant’s events to itself.”
A correlation group is a set of tenants whose activity Identiguard links together. A tenant that is not in a group is isolated: its events are linked only with its own events.
Two notes on the card are important:
- “Workforce and customer identities never correlate with each other, even when their tenants share a group.” Okta and Entra ID are workforce platforms. Auth0 is a customer platform.
- “A change applies to events from now on. Incidents already open keep the group they were opened under.”
The controls
Section titled “The controls”There is no button to create a group. Each tenant is a row with its name, a platform badge and a dropdown.
| Dropdown option | Effect |
|---|---|
| Isolated (default) | The tenant is in no group |
| A group name | The tenant joins that group. Every existing group is listed. |
| New group… | A text box appears with the placeholder Name this group. It is filled in with “Group A”, “Group B” and so on. Type your own name, up to 64 characters. |
Rules for names:
- If you type the name of an existing group, the tenant joins that group. Capital letters do not matter, and a space counts the same as a hyphen.
- If you clear the name, the tenant stays isolated.
The box How these tenants will correlate is a preview. It updates as you edit and shows lines such as Group "Workforce": Okta production, Entra production and Isolated (default): Auth0 customers.
Choose Save groups to save every row at once. You see the message “Groups saved”.
Rename or remove a group
Section titled “Rename or remove a group”There is no rename and no delete.
- To rename a group, move each of its tenants to a new group with the new name.
- A group disappears when no tenant uses it.
- A group with one tenant behaves the same as an isolated tenant.
For steps, see Correlate Okta and Entra ID.
With no tenants
Section titled “With no tenants”The card shows No tenants yet: “Add a tenant to this workspace and it will appear here, isolated until you group it.”
Troubleshooting
Section titled “Troubleshooting”Opening the page and automatic incidents
Section titled “Opening the page and automatic incidents”| What you see | Why | What to do |
|---|---|---|
| A 403 page: “Forbidden: only workspace admins can manage correlation groups.” | You are not an admin of this workspace | Ask an admin to make the change, or to change your role |
| “Not available on the current plan.” with Manage plan | The workspace is not entitled to automatic incidents | Choose Manage plan. Move to Super or add the Automated Identity Incidents add-on. |
| You ticked the master switch but Incidents is still missing | The change was not saved | Choose Save detectors, then reload |
| “Could not save detectors.” | The save failed. Nothing was changed. | Try again |
| “Forbidden: only workspace admins can change incident detectors.” | You are not an admin | Ask an admin |
| “Unknown detector id: …” | The page is older than the current release | Reload the page and save again |
Learned dismissals
Section titled “Learned dismissals”| What you see | Why | What to do |
|---|---|---|
| “Could not save learned dismissal.” | The save failed. The checkbox returns to its old state. | Try again |
| “Loading rules…” | The rules are being loaded | Wait |
| “Rules are shown while automatic incidents are on.” | Automatic incidents are off | Tick the master switch and choose Save detectors |
| “Rules could not be loaded. Reload the page to try again.” | The request for the rules failed | Reload the page |
| No silence rules yet: “Close an incident as a false positive to start teaching this workspace.” | No rule has been armed | Nothing. This is information. |
| “Could not disarm the rule.” | The disarm failed, or the rule no longer exists | Reload the page and try again |
| A rule you disarmed is still in the table | Disarming does not delete a rule | Nothing. Its state is Disarmed. |
Correlation groups
Section titled “Correlation groups”| What you see | Why | What to do |
|---|---|---|
| “Could not save correlation groups.” | The save failed | Try again |
| “A correlation group name may be at most 64 characters.” | The name is too long | Use a shorter name |
| “Every tenantId must belong to this workspace.” | A tenant was deleted while the page was open | Reload the page |
| “A save may carry at most 500 tenants.” | The workspace has more than 500 tenant rows | This is not expected. Report it to the platform team. |
| A message that starts “Failed to synchronize correlation groups” | The groups could not be applied. The save was undone. | Try again. If it continues, report it to the platform team. |
| “Forbidden: only workspace admins can change correlation groups.” | You are not an admin | Ask an admin |
| No tenants yet | The workspace has no tenants | Connect a tenant first |
| Open incidents did not change after you saved | A change applies to new events only | Nothing. New events use the new groups. |