The parent or guardian view.
This future experience sits outside the current adults-only launch and outside staff workspaces.
Future youth support
Future cohort
Intentionally separate from the adults-only launch
Access boundary
Parent access is not part of the adults-only launch and is never inferred from another role.
Designed for the job
The right context. Nothing extra.
A separate, intentionally limited experience being designed for approved youth programs.
01
Limited approved information
02
Support and account notices
03
Separate from staff workspaces
A real working sequence
How the parent or guardian view fits the day.
Availability follows the status shown above. Pilot and in-development workflows are confirmed before a program relies on them.
Design for limited support.
This experience is not part of the current adults-only release.
Keep the scope explicit.
A future youth program would define which account and support notices are appropriate.
Never inherit staff access.
Guardian relationships will remain distinct from coach, care, and administrative roles.
Evaluate the boundary with the workflow
The right context only works when “nothing extra” is specific.
Use the Trust Center to review the permission model, then bring this role into a scoped team conversation.