Player workspace
Your player workspace
The player workspace is a single dashboard for everything a competitor has to keep track of: registrations, teams, the calendar, the watchlist, recruitment, notifications, security, and disputes.
The twelve screens below follow the order a new player usually meets them, from the overview to profile settings.
# Player overview
The overview summarises the whole account on one screen: the current rank, the tournaments available to enter, and the record for every event already joined.
The left navigation is identical across the workspace, so a player can move between tournaments, teams, chat, and settings without coming back here first.
# My tournaments
My tournaments lists every event the player has entered together with its current status, from a pending application through to a published finish.
Counters at the top separate active, completed, and pending entries so the list can be read at a glance.
# Tournament registrations
This is where a team enters an event. The team selector picks the roster, and the registration then runs the backend eligibility, capacity, region, tier, tag, lock, and deadline checks before it is accepted.
Pending applications do not consume capacity. A slot is only taken once a registration is approved or a reserved slot is allocated.
A waitlisted entry is promoted automatically when a slot frees up, in one transaction with the registration count and the notification.
# Group hub
The group hub collects the groups a player has been placed in, with the featured group card at the top and the group chat alongside it.
Group messages stay inside the group, and room credentials are released only according to the opening rule configured for the tournament.
# Private team chat
Private team chat supports replies, unread tracking, and image attachments, and it rolls up into a multi-team inbox for a player who belongs to more than one team.
Access follows current team membership: trials and outsiders are rejected, and uploaded images are stored privately and re-encoded before they are served back.
A reported message can be hidden by an administrator, and a hidden message stops being downloadable.
# Watchlist
The watchlist saves tournaments a player is interested in but has not entered, together with deadline and schedule preferences and private conflict context.
An event that has been entered or has closed simply drops out, so the list only ever holds live interest.
# Recruitment requests
Recruitment requests are the private conversations between a player and a team. Player-to-team applications and team-to-player invitations share the same thread, with messages and accept, reject, cancel, and report states.
Final acceptance revalidates eligibility and capacity transactionally before the membership is added.
# Recruitment community
The recruitment community is the directory of team-recruiting and Looking-for-Team posts, filtered by post type, region, role, and suitability.
Verified player statistics are shown on Looking-for-Team cards, and posting or replying requires a signed-in account.
A rostered player cannot advertise as available, and an opted-out player has their Looking-for-Team post closed automatically.
# Notifications
The communication centre collects platform activity into one inbox with filters, so registration decisions, match notices, and payment updates are not scattered across separate screens.
# Disputes
Disputes are raised from the participant side, with evidence, and each case is scoped to the person and team it belongs to.
A dispute is handled by the Tournament Director or an administrator and can be attributed to a team when that is relevant to the outcome.
Filing a dispute never affects reliability on its own; only attributable, resolved outcomes do.
# Security settings
Security settings manage the account email, its verification state, and the password. An email change is confirmed from the new address before it takes effect.
Verification and reset tokens are random, single-use, and hashed at rest. Raw tokens are never logged.
# Profile settings
Profile settings hold the public-facing details of the account: the display name, the avatar, and the fields shown on a player profile.
Avatars and logos are square with the shared border radius, and uploads are validated and re-encoded before they are stored.