MEDIUM story-peer-mentor-profile-status-peer-mentor-006 2 pts
2
Story Points
Medium
Priority
Peer Mentor Profile & Status Screen
Feature

User Story

As a Peer Mentor (Likeperson)
I want to see all the chapter affiliations associated with my peer mentor account on my profile screen
So that I understand which chapters I am active in, can verify my multi-chapter memberships are correct, and know the scope of contacts and activities available to me

Audience Summaries

NHF operates across 12 national associations, 9 regions, and 1,400 local chapters, with individual peer mentors belonging to up to 5 chapters simultaneously. HLF and Blindeforbundet share similar structural complexity. Without clear chapter affiliation visibility on the mentor profile, volunteers operating across multiple chapters face confusion about which chapter's data they are viewing, leading to support escalations, coordinator overhead, and potential reporting errors. This story eliminates that friction by surfacing every chapter affiliation — with name, region, and active context indicator — directly on the profile screen.

The result is reduced support burden, cleaner multi-chapter reporting, and a platform that scales gracefully to the full organizational complexity of all three partner organizations.

This story depends on story-peer-mentor-profile-status-peer-mentor-001 and carries medium priority. The chapter-affiliations-panel must handle three distinct user states: single affiliation (simple display), multiple affiliations (with active chapter context highlighting), and no affiliations (with coordinator contact path). Stakeholder alignment with NHF is important here — their 1,400-chapter structure means the data model and display logic must be validated against real membership configurations. Acceptance criteria cover all three states and require that the active chapter context be visually distinguished.

QA must test mentors with 1, 2, and 5 affiliations. The 'no affiliations' state requires agreement on the correct coordinator contact path, which is an organizational dependency that should be confirmed before dev begins to avoid a late-stage blocker.

The chapter-affiliations-panel requires querying a mentor-to-chapter membership table that stores chapter_id, mentor_id, role_within_chapter, and a reference to the currently active chapter context (likely stored in session or mentor profile). The display must join to the chapters table to resolve chapter name and to the regions/organizations table to resolve region context. For mentors with multiple chapters, the active chapter must be clearly identified — this likely means reading a selected_chapter_id field from the mentor session or profile record. The no-affiliations zero state needs a coordinator contact path that may require a configurable support contact URL or email per organization.

Conditional rendering must cleanly branch across all three membership states. Ensure the query is scoped to the authenticated mentor and does not leak cross-mentor data. Index on mentor_id in the memberships table is essential given NHF's scale.

Acceptance Criteria

  • Given I am on my profile screen, When the chapter-affiliations-panel loads, Then I see a list of all chapters I am affiliated with
  • Given I belong to multiple chapters, When the panel loads, Then each chapter entry shows the chapter name and region/organization it belongs to
  • Given I have a single chapter affiliation, When the panel loads, Then a single entry is shown without any switcher UI
  • Given I belong to multiple chapters, When I view the panel, Then the currently active chapter context is highlighted or indicated
  • Given there are no chapter affiliations on my account, When the panel loads, Then a message indicates 'No chapter assignments' and provides a contact path to a coordinator

Business Value

Multi-chapter membership is a real and significant complexity in NHF's structure, and peer mentors operating across chapters need clarity about their affiliation scope. Without this visibility, a mentor may incorrectly believe they are missing data or registered under the wrong chapter, leading to support requests and coordinator overhead. Clear chapter affiliation display reduces onboarding friction and supports correct multi-chapter reporting.