feat(postbox): enforce unified inbox separation
This commit is contained in:
@@ -56,7 +56,12 @@ materializing data.
|
||||
|
||||
Users holding several functions may group selected postboxes into unified
|
||||
inbox views. These are query projections only: messages, address, read state,
|
||||
retention, and evidence remain attached to their source postboxes.
|
||||
retention, and evidence remain attached to their source postboxes. Each exact
|
||||
Postbox or template revision may allow grouping, require equal classifications,
|
||||
or remain entirely separate with an administrator-supplied explanation. The
|
||||
rule is re-evaluated on every combined query, including after assignment or
|
||||
policy changes; a View can select a personal projection through the stable
|
||||
`?grouping=<grouping-id>` route parameter without granting access.
|
||||
|
||||
Hierarchy propagation is off by default. Explicit copy, attention/escalation,
|
||||
and shared-visibility rules are distinct, bounded, classification-aware, and
|
||||
|
||||
Reference in New Issue
Block a user