The performance director view.
The performance director workspace begins with a bounded overview. Teams, messages, and named athlete detail remain unavailable unless a separate authorized contract supports them.
Program coordination
Overview
Program coordination without named health data
Access boundary
Every pilot defines whether this is a practitioner or administrative seat before data is shared.
Designed for the job
The right context. Nothing extra.
A program-level overview being built for coordination without silently exposing named athlete health data.
01
Bounded overview shell
02
Teams and messaging in development
03
Separate grants for any named athlete detail
A real working sequence
How the performance director view fits the day.
Availability follows the status shown above. Pilot and in-development workflows are confirmed before a program relies on them.
Define the seat first.
The institution decides whether the performance leader is operating as a practitioner or administrator.
Start with bounded coordination.
The current workspace is an overview shell; Teams and Messages remain in development.
Require a separate approved scope.
Named athlete context appears only when another authorized role and athlete permission both support it.
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.