Skip to content

Add entity severity as a Risk Insights notification trigger condition - #39410

Open
jenny-park-dd wants to merge 2 commits into
masterfrom
jenny.park/risk-insights-severity-notification-conditions
Open

Add entity severity as a Risk Insights notification trigger condition#39410
jenny-park-dd wants to merge 2 commits into
masterfrom
jenny.park/risk-insights-severity-notification-conditions

Conversation

@jenny-park-dd

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Risk Insights notification rules now support setting the trigger condition based on entity severity, in addition to the existing numeric risk score value. Previously, notification conditions supported only a numeric risk score threshold.

This updates step 3 of Configure notifications for Risk Insights to document both options, so users can configure conditions using the same severity labels they see during entity triage.

Merge instructions

Ready to merge.

Additional notes

  • The page already documents severity levels in the Entity severity thresholds section, which is what the in-app See entity severity breakdown by risk score link points to. This change cross-links to that section rather than restating the levels inline.
  • Existing threshold-based notification rules continue to work without changes, so no migration guidance is needed.
  • Available in all regions except GovCloud. The page already carries a site-region notice excluding gov,gov2 from notification rules, so no additional region gating is required.
  • No image changes in this PR.
  • The es translation of this page is untouched and handled by the localization pipeline.

🤖 Generated with Claude Code

Risk Insights notification rules now support basing the trigger condition
on entity severity in addition to a numeric risk score value. Document both
options under Set notification conditions and link to the existing entity
severity thresholds table.

Co-Authored-By: Claude <noreply@anthropic.com>
@jenny-park-dd
jenny-park-dd requested a review from a team as a code owner August 21, 2026 22:40
@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant