Select eligible notification recipients

Purpose

Platform identifies the current, eligible staff recipients from the audience selected by the producer.

How It Works

A producer selects audience entries permitted by the definition. Platform evaluates them when dispatch processes the request. Responsibility lookup contributes current holders, delegates and fallback selections. Role and permission lookup contributes active staff members. Platform unions the results and removes excluded users and, normally, the actor. The recipient limit is checked before eligibility filtering. Customer membership and console-account eligibility prevent cross-customer delivery. Empty and invalid outcomes remain visible even when no notice is created.

The rule rows define this outcome; the acceptance set identifies existing proof and proposed checks. Implementation evidence alone does not approve the observed details.

Relationships

Committed publication supplies the requests processed by this outcome.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Audience selection identifies eligible staff and records why each person qualifies.Ineligible recipients receive no new delivery.
Surfaces: job
Intent sources: services-platform:docs/proposals/notifications/23-decisions.md#D-04services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#PLAT-M23-S07services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#PLAT-M23-S08services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#PLAT-M23-S09

Controls

29 controls apply, from the corpus control catalogue.

TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-002 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Business Rules

8 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 2 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Audience entries select a user, several users, a scoped responsibility, a role or a permission; Definitions restrict accepted types; Empty audiences, unknown types and resource scopes without identifiers are rejected, with allowed types reported for a mismatch. no proof recorded yet	validation	service	test services-platform:modules/notifications/tests/unit/audience-planner.spec.js#refuses a kind the definition does not accept, naming the kinds it does
`02`must prove Confirmed	Recipients are resolved during processing rather than publication; a responsibility transferred before dispatch therefore reaches its current holder. origin: services-platform:docs/proposals/notifications/23-decisions.md#D-04 no proof recorded yet	policy	service	test services-platform:modules/notifications/tests/integration/services/orchestration/resolve-audience.integration.spec.js#changes the people when the responsibility is reassigned between the publish and the dispatch
`03`must prove Proposed	Responsibility lookup supplies current holders, delegates and applicable fallback holders along the requested scope chain; Holding the responsibility in another unit does not qualify a person for this scope. origin: services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#PLAT-M23-S07 no proof recorded yet	calculation	service	test services-platform:modules/notifications/tests/integration/services/orchestration/resolve-audience.integration.spec.js#is the holders of that unit and not the holder of another unit
`04`must prove Proposed	Roles select their active workspace members; permissions select people with active roles granting the permission under authorizer matching; missing roles and ungranted permissions yield no recipients. no proof recorded yet	calculation	service	test services-platform:modules/notifications/tests/integration/services/orchestration/resolve-audience.integration.spec.js#is the people whose active roles grant it, compared as the authorizer does
`05`must prove Proposed	Recipients form a deduplicated union sorted by user identifier; Producer exclusions and the actor are removed unless actor inclusion is requested. no proof recorded yet	calculation	service	test services-platform:modules/notifications/tests/unit/audience-planner.spec.js#leaves out the actor, who is not told of their own act
`06`must prove Confirmed	After exclusions and actor removal, an audience over two hundred is rejected in full; an audience of exactly two hundred is allowed. origin: services-platform:docs/proposals/notifications/23-decisions.md#D-04 no proof recorded yet	validation	service	test services-platform:modules/notifications/tests/unit/audience-planner.spec.js#refuses 201 people as a whole, selecting nobody
`07`must prove Proposed	Eligible recipients are active console users belonging to the workspace's customer; other customers' users, pending invitees and portal users are removed and recorded as isolation refusals. no proof recorded yet	invariant	service	test services-platform:modules/notifications/tests/integration/services/orchestration/orchestrate-request.integration.spec.js#drops a user of another customer, an invited user and a portal user, recording isolation_refused
`08`must prove Proposed	A resolved empty audience finishes as no recipients without producing notices, including when isolation removes every candidate. no proof recorded yet	lifecycle	service	test services-platform:modules/notifications/tests/integration/services/orchestration/orchestrate-request.integration.spec.js#notifies nobody when everyone named is outside the organization, recording no_recipients with the refusal

Scenarios

Id	Given	When	Then	Provenance
`01`	Jane holds Northeast Batch posting and has delegated cover to Sam for a week.	The producer selects responsibility holders at Northeast.	Jane qualifies as holder and Sam as delegate; another unit's holder is excluded.	test services-platform:modules/notifications/tests/integration/services/orchestration/resolve-audience.integration.spec.js#is the delegates of that unit’s holders too, worded as covering the responsibility
`02`	An audience selects a user belonging to a different customer.	Platform evaluates the request.	No eligible recipient remains and History retains the isolation refusal.	test react-console:acceptance/notifications/playwright/journeys/pipeline/NT-ACC-0202.spec.ts#NT-ACC-0202

Planning

Select eligible notification recipients ​

Purpose ​

How It Works ​

Relationships ​