The administrator view.
The administrator has a bounded workspace lifecycle plus organization-only People and Requests directories. Invitation, member mutation, and audit tooling remain in development.
Team operations
Workspace
Operations without athlete health data
Access boundary
Administrators do not receive individual readiness, RED-S, domain, or athlete-note data.
Designed for the job
The right context. Nothing extra.
Handle workspace lifecycle, people, and requests without turning an operations seat into health-data access.
01
Workspace lifecycle
02
Organization-only People and Requests directories
03
No health-data access by role alone
A real working sequence
How the administrator view fits the day.
Availability follows the status shown above. Pilot and in-development workflows are confirmed before a program relies on them.
Enter a non-clinical workspace.
The workspace lifecycle preserves the administrator boundary without implying athlete health access.
Review People and Requests.
Organization-only directories expose the operational records the role needs while member and invitation mutations remain in development.
Maintain roles—not clinical permissions.
Athlete and practitioner consent boundaries remain outside the administrator seat.
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.