Hearpeers Community — User Tasks by Role

For GUI mapping and flowchart · March 2026 · Last updated: 2026-05-22
Source of truth: current codebase — extracted by Lucas Maieski (Coopers Digital), March 2026
Based on current implementation (Lucas Maieski's RBAC extraction) cross-referenced with the original role/journey spec. Updated 2026-05-20 with Anna Breitfuss's reply on Q-01–Q-06. Updated 2026-05-21: applied Anna Breitfuss post-meeting confirmations (AW 09:49 + WG 14:07). Q-02 nuance: My Groups fully interactive for Candidates; Discover Groups view-only with contextual note + Join disabled. Q-06 expanded: AM can update role permissions within own area (Member→Mentor upgrade) + export own-area users. Mentor connection model confirmed (Option A + 14-day AM safety-net). Moderator assignment confirmed: (a) Group Admin + Super Admin, (b) wp-admin + Community Settings frontend. Anomaly #1 resolved: Recipients post standard only — AM reposts as FAQ. Connections filter logic spec received from Anna. Use checkboxes to track mapping progress.  ⚠️ = needs further clarification.

Open items — pending clarification

# Item Status Who to ask
8 "MED-EL" as a connectable role — UI label confirmed as "MED-EL (area manager)". Broader topic: differentiation of MED-EL staff in general vs area managers who manage a specific country/area (separate MED-EL documentation shared by Anna, 2026-05-21). Confirmed UI label (Anna, 2026-05-21) MED-EL — staff differentiation still evolving
9 "Moderator" group sub-role — scope, assignment mechanism, UI exposure Confirmed (Anna, 2026-05-21) Lucas — BuddyPress role-change UI investigation
(a) Who assigns: both Group Admin (Area Manager) and Super Admin. (b) UI exposure: both wp-admin and Community Settings frontend. BuddyPress backend role-change UI (Member / Moderator / Administrator within a group) confirmed to exist but not yet fully functional per Anna's testing — Lucas to investigate.
10 Connections filter — which filter options does each role see? Answered (Anna, 2026-05-21 WG) Lucas — implementation
Recipients filters: Location, Language, Community Role, Implant Type, Interest, Name. Default order: location → language → implant type → interest → role. Candidates filters: Location, Language, Implant Type, Interest, Name (no Role filter). Default sort: location nearby first. My Connections: AM pinned; same-area Mentors shown; worldwide findable; unrelated staff hidden. See PRD FR9.5 for full spec.
11 Invitations scope Closed (Anna, 2026-05-20) —
Area Manager + Super Admin only, via Community Settings UI. Effectively gated; Lucas to verify no non-UI bypass.
12 "Manage community options" scope for Area Manager (Q-06 partial) Partially open MED-EL
Q-06 expansion (Anna, 2026-05-21): AM can update role permissions within own area (Member→Mentor upgrade) + export own-area users. Specific definition of "Manage community options" as a named capability in Community Settings UI remains to be proposed and confirmed.
13 Mentor connection model Confirmed (Anna, 2026-05-21) —
Confirmed: Option A LinkedIn-style request-with-message (500 chars, required; placeholder copy guides the user) + "New in your area" discovery surface (Notification Strategy v3 §5.3, bell-only, once per session, only if new) + 14-day AM safety-net (Area Manager notified if Mentor leaves request unanswered for ~14 days). Required Mentor response with polite decline template; pending-request reminder fires after 5 days. AM auto-connection preserved (no request flow for Candidate→AM or Recipient→AM — they are auto-connected at registration).
Role 1

Candidate

Self-registered user. Pre-implant, newly diagnosed. Most restricted role — acts as a "preview" of the community with a guided path toward becoming a Recipient. Every user who registers is assigned an area at registration, connected to their Area Manager, and added to their area's Candidate group. Note: The "Caregiver" label has been removed (MED-EL, 31 Mar 2026). Caregivers who register via MyMedEL are assigned the Recipient role automatically.

Account & Onboarding

Connections

✅ Confirmed: Candidates can only see and connect with Mentors (can_see_connection_mentor, add_friend_mentor). No access to Recipient, Area Manager, or Super Admin profiles.

Groups

Posts & Feed

Chat & Messaging

Profile

Role 2

Recipient

Confirmed MED-EL cochlear implant user. Core community member. Full participation in groups, feed, and connections.

Account & Onboarding

Connections

Groups

Posts & Feed

Comments

Chat & Messaging

Profile

Role 3

Mentor

Experienced Recipient who supports Candidates and community members. Moderation powers within groups. Primary point of contact for question-answer flows.
Includes all Recipient tasks. Only additions and differences are listed below.

Account & Onboarding

Groups

Posts & Feed

Comments

Chat & Messaging

Profile

Role 4

Area Manager

Regional coordinator. Manages users, groups, and community operations within a defined area. Administrative access to WordPress backend.
Includes all Mentor tasks. Only additions are listed below.

Connections

Posts & Feed

Chat & Messaging

User Management (via WordPress backend)

Administration

Role 5

Super Admin

Full platform administrator. MED-EL-side governance role with access to all content, all users, and all platform configuration.
Includes all Area Manager tasks. Only additions are listed below.

User Management (via WordPress backend)

Administration

Cross-role Tasks

Available to every logged-in user regardless of role.

Notes

Moderator group sub-role

Confirmed (Anna Breitfuss, 2026-05-20/21): A Mentor (or other non-admin role) can be assigned as moderator of a specific group. When assigned, they CAN edit and delete posts and comments within that group only. The default Mentor role retains no moderation rights. This is distinct from the formal Group Admin role (Area Manager + Super Admin). Assignment confirmed (2026-05-21): (a) both Group Admin and Super Admin can assign the Moderator sub-role; (b) UI exposure via both wp-admin and Community Settings frontend. Lucas investigation needed: BuddyPress backend role-change UI (Member / Moderator / Administrator) confirmed to exist but not yet fully functional per Anna's testing.

Future features (confirmed by MED-EL, not yet built)