TOURNAMENTSUITE
TOURNAMENTSUITE
Help CenterPlatform OverviewProducts, Roles, and How They Fit TogetherWhat Is Tournament SuiteCreate Your AccountQuick-Start: Your First TournamentCreate a ProjectProject DashboardProject Settings: General and AppearanceManage Team and RolesCircuits and SeasonsCreate a TournamentTournament Settings OverviewRegistration SettingsParticipant and Match RulesSet up tournament structure and formatsSeed and place participantsSchedule matchesPublish and Go LiveDuplicate a tournamentUse and manage tournament templatesManage RegistrationsCheck-InCustom FieldsExport ParticipantsMonitor and Control a Live TournamentApply Interventions to a MatchTrack and Resolve Issues During a Live EventHandle Officiating and Formal DisputesSet Up Streams and the Broadcast CenterSet Up Branding and SponsorsReview your project's financial activityConfigure prize pools and approve payoutsSet up your payout methodHold prize funds in escrowManage project communications from the hubCreate and send campaigns to participantsCreate and manage API keysReceive real-time event notifications with webhooksConnect Tournament Suite to a Discord serverManage Tournament Permissions and Staff AccessFile and Track Governance Cases With Your ProjectConfigure Wellness Settings for Your ProgramProjects, Workspaces, and Team ManagementTournament Creation, Settings, and StructuresLive Operations, Broadcast, Streams, and MediaGovernance, Support, Integrations, and Organization ControlsPublic Discovery and Viewer Experience

Products, Roles, and How They Fit Together

Tournament Suite is made up of four main product surfaces that work together around the same competitive programs.

Tournament Suite is made up of four main product surfaces that work together around the same competitive programs.

The Four Product Surfaces

Organizer Workspace

This is the working environment for organizations that create and run competitive programs.

It is used to:

  • set up projects and tournament portfolios,
  • configure tournament settings, structures, participants, and schedules,
  • control branding, streams, sponsorships, and communications,
  • manage live operations, finance, prize flows, support, and governance.

Typical users:

  • project owners,
  • organizers,
  • operations leads,
  • broadcast managers,
  • finance managers,
  • referee or governance leads.

Player Experience

This is the public and authenticated experience for players, teams, viewers, and broader community members. It is available both as a web experience and as the Arena Desktop app, a downloadable client that provides the same player account and match experience outside the browser.

It is used to:

  • discover tournaments, matches, circuits, venues, and highlights,
  • manage participation, teams, match rooms, progression, and purchases,
  • use matchmaking, LFG, recruiting, scouting, coaching, and social features,
  • complete verification, guardian, transparency, and wellness workflows.

Typical users:

  • guests and viewers,
  • registered players,
  • team captains,
  • parents or guardians,
  • creators, coaches, scouts, and competitive community members.

Admin Control Center

This is the internal operating environment for platform staff.

It is used to:

  • manage users, projects, tournaments, subscriptions, and revenue,
  • monitor system health, queues, audits, and platform-wide analytics,
  • handle moderation, compliance, transparency, school programs, and risk control,
  • oversee monetization, communications, support, feedback, and developer operations.

Typical users:

  • administrators,
  • moderators,
  • analysts,
  • support teams,
  • compliance teams,
  • finance teams,
  • operations engineers,
  • internal product or growth teams.

Sponsor Portal

This is a separate authenticated workspace for brand and sponsor accounts rather than tournament organizers or players. Unlike the organizer workspace, it is not scoped to a single tenant — sponsor accounts can discover and evaluate competitive talent across the platform, subject to profile visibility settings.

It is used to:

  • discover and evaluate competitive talent for sponsorship,
  • create and manage advertising campaigns,
  • manage sponsorship contracts,
  • track spend and performance analytics.

Typical users:

  • brand and sponsor account managers,
  • campaign managers,
  • analytics and finance contacts on the sponsor side.

Shared Operating Layers

The four product surfaces rely on the same shared business foundation.

Identity And Access

Users sign in once and then access the parts of the platform that fit their role, permissions, and verification status. Organizer workspaces and admin surfaces also apply deeper capability-based access control.

Competition Data

Projects, tournaments, participants, matches, structures, standings, circuits, and reporting are all part of one shared competition model. Each surface uses it differently:

  • organizers configure and control it,
  • players consume and participate in it,
  • admins supervise and intervene in it.

Money Movement

Commercial features connect across products:

  • organizers manage prize rules, billing, and financial reporting,
  • players use wallet, shop, inventory, marketplace, payouts, and billing,
  • sponsors manage campaign spend, contracts, and performance analytics,
  • admins oversee revenue, subscriptions, risk, and disputes.

Trust And Governance

Integrity, verification, guardian approval, wellness, compliance, moderation, appeals, and transparency are not isolated tools. They shape who can participate, what actions are allowed, and how issues are resolved across all products.

Common Role Patterns

  • Guest: browses public information, tournaments, matches, highlights, and venues.
  • Player: joins competitions, manages profile activity, uses rewards and social tools.
  • Team Manager: coordinates teams, recruiting, scrims, and roster-related activity.
  • Organizer: configures tournaments and controls event execution.
  • Referee or Moderator: reviews reports, disputes, and rulings.
  • Guardian: manages consent, student linking, and controls for younger participants.
  • Admin: supervises the platform at an operational level.
  • Analyst: uses metrics, exports, and performance views.
  • Support or Compliance Lead: handles cases, policies, tickets, financial checks, and regulatory workflows.
  • Sponsor or Brand Manager: discovers talent, runs ad campaigns, and manages sponsorship contracts and spend.

How The Products Fit During A Real Event

  • an organizer creates a project and launches a tournament in the organizer workspace,
  • players discover the event and interact with it through the player experience, on the web or through Arena Desktop,
  • sponsors evaluate and support competitive talent and campaigns through the sponsor portal,
  • live operational staff monitor activity, resolve issues, and intervene when necessary,
  • internal admin staff oversee platform integrity, financial movement, compliance obligations, and system health.

That cross-product flow is described in the Help Center.

Was this helpful?

Platform Overview

Tournament Suite is a connected platform for running competitive programs from planning to live execution to post-event reporting.

What Is Tournament Suite

An overview of Tournament Suite, its white-label multi-tenant model, and the surfaces organizers, players, sponsors, and developers use.

On this page

The Four Product SurfacesOrganizer WorkspacePlayer ExperienceAdmin Control CenterSponsor PortalShared Operating LayersIdentity And AccessCompetition DataMoney MovementTrust And GovernanceCommon Role PatternsHow The Products Fit During A Real Event