docs(usage): document notification triggers and asset-scoped filters (#6937) - #7680
Conversation
Rewrite the notifications guide for live and digest triggers, resource types, events, filters, and notifiers. Findings docs now say assets cover every inventory category except security platforms.
Contributor License Agreement✅ CLA signed 💚 Thank you Abdullah (@AzazelSensei) for signing the Contributor License Agreement! Your pull request can now be reviewed and merged. We appreciate your contribution to Filigran's open source projects! ❤️ This is an automated message from the Filigran CLA Bot. |
|
Thank you for your contribution. This PR is but one step away from being ready for merging: all commits must be PGP-signed. To get started, please see https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits |
Filigran Automation (Filigran-Automation)
added
the
community
Filigran Automation (Filigran-Automation)
changed the title
There was a problem hiding this comment.
Pull request overview
This PR updates the user-facing documentation to reflect the current Notifications (triggers + notifiers, live + digest) and clarifies that Findings and related filters are asset-scoped across all inventory categories except security platforms.
Changes:
- Rewrites the Notifications usage guide to explain triggers (live/digest), resource/event types, filters, and notifiers (UI/email/webhook).
- Updates the Findings guide to clarify “Impacted assets” terminology and that findings can attach to assets across the unified inventory (excluding security platforms).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/docs/usage/notifications.md | Rewritten guide for configuring triggers/digests, resource/event types, filters, notifiers, and the in-app notification center. |
| docs/docs/usage/evaluate/findings/findings.md | Clarifies asset scope (all inventory categories except security platforms) and updates wording to “Impacted assets”. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| | Finding | Asset filters cover every asset category except security platforms | | ||
| | Asset | Hosts, cloud resources, web applications, AI targets, and the other inventory categories | |
| | Creation | A new entity of the selected type is created | | ||
| | Modification | An existing entity is updated | | ||
| | Deletion | An entity is deleted | | ||
| | Score degradation | Only for **Scenario**. A Simulation score drops below the previous run of the same Scenario (the former notification-rule trigger) | |
Proposed changes
Testing Instructions
docs/docs/usage/notifications.mdanddocs/docs/usage/evaluate/findings/findings.md.Related issues
Checklist