Subscription granularity should reach specific objects rather than offer only all or nothing
Aliases: fine-grained notifications · selective following · object subscription
What it is
Object-level notification subscription lets people follow only the documents, passages, issues, tasks, or threads relevant to their work instead of choosing between every event in a space and complete silence. Granularity determines which objects enter a person's information stream; it does not determine how strongly different event types should interrupt them.
Why it happens
Collaborative spaces produce many changes irrelevant to any one member. Workspace-wide delivery dilutes useful signals, while muting everything hides dependency changes. Object scope uses members' local knowledge of responsibility and interest. The comprehensibility of that scope depends on hierarchy, inheritance, stable identity, and what happens when objects move.
Studying it
Compare workspace, object, and rule-based subscription on recall of relevant events, irrelevant-message share, handling latency, and configuration cost. Include moving, nested, and reassigned objects to test whether participants can predict the effective set. Click-through alone confounds information value with headline attraction.
Where it stops holding
Safety alerts, access changes, and direct obligations cannot depend entirely on manual following. Per-object configuration becomes expensive at high scale, and ephemeral objects may lack stable identity. Role rules, inheritance, and explicit exceptions are preferable to an unlimited collection of switches.
Applying it
- Put follow controls beside objects and identify manual, role-based, inherited, and participation-based sources.
- Support hierarchical scope previews and explain what changes when an object moves.
- Isolate mandatory events and state why they bypass ordinary following preferences.
- Evaluate both missed obligation events and irrelevant-message share rather than optimizing reduction alone.
Related
- Same group: V4.03.2 Default intensity by event type · V4.03.3 Default subscription scope · V4.03.4 Scheduled digests · V4.03.5 In-notification unsubscribe
- Adjacent: V6.05 Notification and Collaboration Noise · V3.07 Permissions and Sharing Scope
- Search terms:
notification subscription·object-level following·selective awareness
Cards in the same group
- V4.03.2Mentions, assignments, and observed events need different default intensities
- V4.03.3Default subscription scope determines what most people actually receive
- V4.03.4Scheduled digests can replace event-by-event delivery without discarding information
- V4.03.5Unsubscribe controls should appear with the notification itself