Review a Team Enrollment
Approve or decline a Team’s request after checking the actual Roster seats.
- Who this is for
- League Owners and Organizers
- When you’re done
- The request is approved into a Roster or declined with a clear reason.
1. Open the requests
Open your League, choose Manage League, then Rosters & enrollments. Find the pending request and choose Review.
2. Check the Team and region
Confirm the Team, requested Roster name, and region. Check your League's entry rules before approving; an approved relationship is not proof that every Member is eligible to compete.
3. Review the seats
The preview shows who would be rostered, who would be reserve or blocked, and why. Resolve missing identities or Memberships with the Captain where needed.
For a claim of an existing Roster, all current Roster members must have joined the Team before approval. Legacy direct Roster removals are retired. If an incumbent must not play in this League, an Owner or Organizer can apply an explicit, audited player block below; do not silently bypass consent. If existing Members would lose seats, review that displacement and explicitly confirm it. Do not use approval to silently remove players.
4. Approve or decline
Choose Approve to create or adopt the Roster. Choose Decline and provide a useful reason if the request should not proceed.
If Heir says the preview changed, reload the preview and review it again. The Team or Roster changed while you were deciding; your earlier preview is no longer current.
5. Verify the result
Check the Enrollment's status, Roster link, and seat counts. An approved Enrollment can still be Incomplete until enough eligible Members meet the game's minimum match-roster requirement; it can be Incomplete even when the Roster still has unused capacity. Ask the Roster Captain to set availability before scheduling it.
Policies and ongoing management
Under Rosters & enrollments, Owners and Organizers can control whether the League accepts requests, whether eligible new requests are approved automatically, and whether Roster changes are locked. Existing Enrollments can be suspended, resumed, refreshed, or withdrawn.
A roster lock defers seat fills; departures and Organizer eligibility blocks still take effect. Competition locks can also postpone changes during a running tournament. See Teams and Enrollments for the detailed rules.
Block or restore a player's eligibility
Under Rosters & enrollments → Player eligibility, choose Block a player, search by name or Discord ID, and review their identity. Enter a reason and confirm. The player and affected Team Captains receive the reason, and the change is recorded in the League audit log.
The block releases the player's current Seats in this League, even while Rosters are locked. It persists through automatic Roster updates, Team changes, and leaving and rejoining the League. Independent Team membership, Team ownership, other Leagues, and historical results are unchanged. This is not a Discord ban or a game-server kick.
Existing tournament lineup snapshots stay intact. A lineup containing a blocked player must be updated before starting the tournament or reporting scores. New lineup selection cannot include them.
To restore eligibility, choose Review block → Lift block, enter a reason, and confirm. Normal capacity, identity, cooldown, and lock rules still apply; lifting a block does not guarantee a Seat. Legacy Seats are not automatically restored or converted.
For a skipped conversion or pending legacy claim, blocking an incumbent releases their current legacy Seat. Review a fresh claim preview afterward. It does not assign Team ownership or restore retired standalone-Roster commands.
Next: Publish a schedule or run a tournament.