Any authenticated person asking what an action means or who may perform it.
Primary/co-manager apply to a team association; commissioner composes with either role or seatless membership.
HELP TOPIC // getting-started
/roles-primary-co-manager-and-commissioner · corpus 0.1 · verified 43c1c50
Roles: primary manager, co-manager, and commissioner
Roles are separate authorization axes; commissioner capability is an overlay.
Sources
Who can use this answer.
Read the current gate
Viewer state and action authorization are persisted and evaluated together.
The label carries the consequence.
Absent, primary, co-manager, seatless commissioner, and pending co-manager are not interchangeable.
Use the runtime clock
Role/invitation expiry uses configured runtime policy.
Keep the right audience
Role projections avoid unauthorized identity/invitation details.
Take the next safe step.
- →
Read the role label.
- →
Use the local disabled reason.
- →
Keep seat responsibility and commissioner authority separate.
- →
Ask for an audited correction instead of sharing credentials.
Know what changes.
What happens
A commissioner may oversee a league without owning a roster; a co-manager is not the primary manager.
What can be undone
Role changes use explicit confirmation and audit.
What you should see
The interface exposes allowed action, disabled reason, or valid request route.
Keep context. Do not replay blindly.
Permission-denied preserves state and protected details.
Follow the help link/return target; never retry a forbidden mutation as another role.
One concrete read.
Example: A seatless commissioner receives seatless base help plus commissioner overlay.
Runtime source: Persisted membership/role, commissioner authorization, co-manager capability, and action policy.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.