HearPeers Community — User Tasks by Role

For GUI mapping and flowchart · March 2026
Source of truth: current codebase — extracted by Lucas Maieski (Coopers Digital), March 2026
Source note: The November 2025 spec (Carlos Souza & Lincoln Alves) was aspirational — written before the platform was built. Where it conflicts with the code, the code wins. Those conflicts are open questions to resolve with the team and MED-EL.
Use checkboxes to track mapping progress.  ⚠️ = open question — needs confirmation from Coopers team or MED-EL.
Groups are also referred to as "Clubs" in earlier documentation.

Open Items Before Finalising Flows

# Item Who to ask Status
1 Candidate chat restriction — can they only message Mentors, or any user? MED-EL (Julia / Alexandre) ✅ Confirmed
Messaging requires a connection, no role restriction. Candidate can only message users they're connected with (i.e. Mentors).
2 Candidate profile photo — intentionally blocked or a bug? MED-EL Open
3 Candidate feed access — no default posts visible, no comments. Intentional "paywall preview"? MED-EL Open
4 Pin posts — Mentor or Area Manager+? Spec vs implementation conflict. Lucas (dev) Open
5 Auto-response message — Mentor or Area Manager+? Spec vs implementation conflict. Lucas (dev) Open
6 CSV export and invitations — restrict to Area Manager+? GDPR concern. MED-EL + Gabi ✅ Confirmed
CSV export fixed: now restricted to Area Manager and Super Admin only (Lucas, 2026-03-12). Invitations still open.
7 Connection visibility matrix — who can see and connect with whom across all role combinations. Lucas (dev) ✅ Confirmed
See matrix in rbac-permissions-by-section. Each role sees all roles below it + its own.
Role 1

Candidate / Caregiver

Self-registered user. Pre-implant, newly diagnosed, or caregiver. Most restricted role — acts as a "preview" of the community with a guided path toward becoming a Recipient.

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

⚠️ Cannot join area-specific groups (no area assigned at Candidate stage)

Posts & Feed

⚠️ Cannot create regular posts, comments, or see default feed posts — confirm if intentional

Chat & Messaging

✅ Confirmed: Messaging requires authentication + an existing connection. Since Candidates can only connect with Mentors, in practice they can only message Mentors. No role-based cap — the connection itself is the gate.

Profile

⚠️ Cannot upload a profile photo (backend restriction — confirm if intentional)
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

⚠️ Configure automatic response message — spec grants this to Mentors; current implementation restricts to Area Manager+

Groups

Posts & Feed

⚠️ Pin a post in a group — spec grants this to Mentors; current implementation restricts to Area Manager+

Comments

Chat & Messaging

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

⚠️ Send community invitations — currently open to all roles; confirm intended scope
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.