Participate in committee work through the member portal

Purpose

Committee participants need to follow the work relevant to them and act in their own name. These portal operations connect meeting preparation and invitations to asynchronous decisions while limiting what each caller can read or change.

How It Works

A signed-in caller linked to a contact asks for their meetings or opens an available meeting directly. The meeting page includes preparation information according to publication and audience checks. Current committee participants and people recorded on the meeting receive a broader meeting view than other portal readers, including its video details. Staff notes are omitted from meeting pages, although calendar descriptions require separate consideration. A recorded participant can answer their invitation, and a meeting chair or liaison can help another participant or record attendance. Those portal changes stop when the meeting ends. Minutes become readable in the permitted audience after circulation, and even public minutes visibility uses an authenticated portal operation. For a readable decision, the caller sees the motion, the explained rule and their own participation information. An eligible caller can submit a recorded asynchronous vote using their own appointment. After the decision closes, the page provides the result and explanation. Inaccessible meetings, draft decisions and other denied record reads appear missing. The product should reconcile these active operations with the recorded decision to disable meeting access until the deferred portal stage.

Relationships

Meeting scheduling supplies the records participants follow.
Decision management owns the motion, eligibility snapshot and recorded votes.
Recusal management lets an eligible participant declare their own conflict.

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: Participants can locate the gatherings and papers relevant to themPortal answers respect the applicable audienceEligible voters can submit their own asynchronous votes
Surfaces: portalapi
Preconditions: The caller has a portal session linked to a contact, unless using the anonymous public meeting operation.
Intent sources: services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D11services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#N1services-committees:docs/milestones/README.md

Controls

24 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-SEC-001 TC-SEC-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-AVL-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`committees.portal.participate`	api	tenant

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	A portal session linked to a contact can read non-draft public and members-visible meetings, while participants-visible meetings require a current committee appointment or meeting participant record; denied reads appear missing. no proof recorded yet	permission	service	observed services-committees:modules/meetings/services/portal/portal-meetings.ts:portalMeeting
`02`must prove Proposed	Anonymous public meeting reads return the meeting identity, title, committee name, kind, schedule, time zone, approved textual location fields and status without staff notes or video information. no proof recorded yet	permission	service	test services-committees:modules/meetings/tests/unit/services/public-meeting.spec.ts#shows the public page exactly the allow-listed fields
`03`must prove Proposed	Portal meeting responses always omit staff notes and expose video information only to current committee participants or recorded meeting participants. no proof recorded yet	permission	service	observed services-committees:modules/meetings/services/portal/portal-meetings.ts:pageFor
`04`must prove Proposed	The personal meeting list uses a window ending after it begins, defaulting from today to ninety days ahead. no proof recorded yet	validation	api, service	observed services-committees:modules/meetings/services/portal/portal-meetings.ts:myMeetings
`05`must prove Proposed	A meeting participant may answer their own invitation, while a chair or liaison recorded on that meeting may answer for others or record attendance; ended meetings reject these portal changes. no proof recorded yet	permission	service	observed services-committees:modules/meetings/services/portal/portal-meetings.ts:rsvp
`06`must prove Proposed	Authenticated portal users see circulated, approved or amended minutes according to minutes visibility, defaulting to the committee’s current participants or the meeting’s recorded participants, and never see draft minutes. no proof recorded yet	permission	service	observed services-committees:modules/meetings/services/portal/portal-minutes.ts:portalMinutes
`07`must prove Proposed	The readable decision page supplies the motion, plain-language rule, personal eligibility, recusal and vote, recorded asynchronous votes and the closed tally, while drafts and inaccessible decisions appear missing. no proof recorded yet	permission	service	observed services-committees:modules/decisions/services/portal/portal-decisions.ts:portalDecision
`08`must prove Proposed	Only eligible voters can read a confidential decision through the portal. no proof recorded yet	permission	service	observed services-committees:modules/decisions/services/portal/portal-decisions.ts
`09`must prove Proposed	Portal voting accepts an eligible person’s own appointment once on an open recorded asynchronous decision. no proof recorded yet	validation	service	observed services-committees:modules/decisions/services/persistence/decisions.ts:castVote
`10` Proposed	The personal decision list returns decisions linked to the caller’s eligible appointments in descending creation order, with an optional open-only filter and a voted indicator.	policy	service	observed services-committees:modules/decisions/services/portal/portal-decisions.ts:myDecisions
`11`must prove Proposed	The product should keep public and portal meeting operations disabled until the portal milestone and review their availability then. origin: CMTE-M3 D11 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions) no proof recorded yet	policy		documented services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions
`12` Proposed	The product should reserve meeting, minutes and action-item work for the member portal stage. origin: CMTE-M3 N1 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions)	policy		documented services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions
`13`must prove Proposed	An invitation response requires an invitation status or attendance value and rejects a target who has no participant record for that meeting. no proof recorded yet	validation	service	observed services-committees:modules/meetings/services/portal/portal-meetings.ts:rsvp

Scenarios

Id	Given	When	Then	Provenance
`01`	A meeting has a voting director, a non-voting adviser and an unrelated portal caller	Each requests its participants-visible portal page	The voting participant can read confidential agenda items, the adviser cannot, and the unrelated caller cannot read the meeting	observed services-committees:modules/meetings/services/participation/participation-rule.ts:mayReadConfidential

Planning

Participate in committee work through the member portal ​

Purpose ​

How It Works ​

Relationships ​