Summary
When joint-class history (#138) is visible, each session row should show the instruktør's name — not just their email. This requires a `display_name` field on the user profile and a safe way to expose it to co-instruktører at the same gym without leaking unrelated personal data.
Priority
Low (blocked by #138 — shared sessions must be visible before names matter)
Data model
-- Extend existing profiles table (or create one if it doesn't exist)
alter table profiles add column display_name text;
RLS: `display_name` should be readable by anyone at the same gym (same `sporty_business_unit_id` via `user_gyms`); only the owner can update it.
UI spec (Carbon g100)
Acceptance criteria
Out of scope
- Profile photos / avatars
- Display name visible outside the same gym
Summary
When joint-class history (#138) is visible, each session row should show the instruktør's name — not just their email. This requires a `display_name` field on the user profile and a safe way to expose it to co-instruktører at the same gym without leaking unrelated personal data.
Priority
Low (blocked by #138 — shared sessions must be visible before names matter)
Data model
RLS: `display_name` should be readable by anyone at the same gym (same `sporty_business_unit_id` via `user_gyms`); only the owner can update it.
UI spec (Carbon g100)
Acceptance criteria
Out of scope