Platform
Roles and permissions
Role is not an afterthought. It decides which surfaces open, which changes you can make, and which tools an agent loads.
Who it is for
Set by the head coach, general manager or operations.
How this is handled today
Permissions get treated as a setting rather than a design. Everyone is given more reach than the job needs because it is easier than working out the boundary, and health and cap records end up one click from people who should never see them.
Assistants make it worse. A tool acting on someone's behalf usually runs with wider reach than the person who asked for it, which quietly turns delegation into escalation.
What changes
Role decides which surfaces open, which changes you can make, and which tools an agent loads. A position coach is not served the cap at all, rather than being shown an empty version of it.
An agent inherits exactly its holder's reach and no more, so asking for help can never widen what you can see.
What you do here
- Gate surfaces, so a position coach is not served the cap at all
- Gate mutations, so only the right seats approve a decision
- Gate agent tools, so an agent inherits exactly its holder's reach
What it reads
- Staff
- Assignments
- Decisions