Skip to content

docs: notifications follow every organization membership #15628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
devGregA wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

docs: notifications follow every organization membership #15628

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/content/asset_modelling/engagements_tests/PRO__organizations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,6 +123,13 @@ Findings) with the permissions that role grants. Pinning an Asset into an
Organization therefore extends visibility, which is why creating a pin requires edit
permission on **both** the Organization and the Asset.

**Notifications follow the same rule.** Notifications about an Asset — and about its
Engagements, Tests, and Findings — reach the members of every Organization the Asset
belongs to, not only its primary one, subject as always to each user's own
notification preferences. So pinning an Asset into a Compliance Scope Organization
also makes that scope's members an audience for its findings, and removing the
membership removes them again.

### Managing memberships

- The Organization view gains a **Member Assets** table listing every member with
Expand Down
Loading