An admitted member viewing a team or an authorized manager changing its roster.
All modes; roster zones and limits are selected from configured league state.
HELP TOPIC // getting-started
/teams-team-seats-and-rosters · corpus 0.1 · verified 43c1c50
Teams, team seats, and rosters
A team is the durable football object; a team seat is the responsibility shared by its managers.
Sources
Who can use this answer.
Read the current gate
Admission is required for team data; a persisted association is required for roster mutation.
The label carries the consequence.
Seatless, primary, co-manager, claimed, open, full, locked, and unavailable are distinct.
Use the runtime clock
Roster/lineup deadlines derive from each player's kickoff and league timezone.
Keep the right audience
Team-scoped details follow the league visibility policy.
Take the next safe step.
- →
Confirm team display identity and seat role.
- →
Read roster slots and capacity.
- →
Use Team for lineup/roster and Players for acquisition.
- →
Refresh after a commissioner correction.
Know what changes.
What happens
A roster belongs to a team, not one identity; a seatless member cannot mutate it.
What can be undone
Unlocked lineup changes can be revised; kickoff and final boundaries are authoritative.
What you should see
The result names team, slot, player, and saved/locked state.
Keep context. Do not replay blindly.
Capacity, authorization, lock, and stale failures make no partial change.
Return to /team, reread week/locks, and use commissioner help for a wrong association.
One concrete read.
Example: A seatless member may read rules but is not told to edit a roster they do not own.
Runtime source: Roster config, teams/memberships/rosters, schedule kickoff, and lineup processor.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.