Projects, Workspaces, and Team Management

Projects are the top-level operating units in the organizer workspace. A project is where an organization groups its tournaments, staff access, branding, communications, financial settings, and long-term program controls.

What A Project Includes

A project acts like a business workspace for an organizer. Within one project, teams can manage:

• tournament portfolios,
• project-specific branding and identity,
• staff roles and access,
• financial reporting and billing context,
• communication strategy,
• wellness and safety settings,
• circuit-level competition programs.

This structure lets one organization operate multiple tournaments without rebuilding its settings each time.

Project Dashboard

Each project has a dashboard that gives organizers a quick operating snapshot.

The dashboard focuses on:

• total tournament volume,
• events currently live,
• completed tournaments,
• total participant volume,
• total matches played,
• team member count,
• recent tournaments,
• a recent activity feed,
• quick actions into settings and tournament creation.

Team management is one click away from the dashboard's members panel, but it is not a dashboard-level quick action itself. In business terms, the dashboard acts as the project command summary rather than a deep operational workspace.

Workspace Modules

Projects expose different workspace modules depending on access, plan, and role. In practice, this creates a modular operating environment that can show or hide dozens of areas depending on what a project has enabled, including:

• core operations — overview, tournaments, settings, team, analytics,
• competitive programs — circuits, rankings, matchmaking, scrims, ladders,
• player-facing systems — battle pass, progression, fantasy, coaching, mentorship, scouting,
• commerce — marketplace, wallet, payouts, financials,
• games infrastructure — game server rentals, game automation, discipline configuration,
• community and safety — wellness, guardian controls, moderation, support,
• growth — developer portal, custom domains, website builder, widgets, creator program,
• specialized programs — cloud gaming, Web3, dating, academy.

This matters for partners because the organizer experience is not flat. It can be shaped by plan level, project state, and role permissions — a given project only shows the modules it is actually entitled to.

Team And Staff Management

Projects support shared operation by allowing organizers to manage who can work inside a project.

Typical staff responsibilities include:

• owners who control the project as a whole,
• admins who manage operations and settings,
• editors or operators who work on tournaments and execution,
• moderators or specialized staff for governed activity,
• viewers with limited read-only access.

From a partner perspective, this makes Tournament Suite usable by real operating teams rather than a single individual.

Project Settings

Project settings are split into practical operating areas rather than one general form.

These settings cover:

• general project information,
• appearance and branding,
• billing and commercial setup,
• team and member management,
• wellness and policy controls.

This lets a partner treat the project as an ongoing competitive program with its own identity and operating rules.

A dedicated feature flags page lets organizers see, at a glance, which capabilities are turned on for the project — whether a feature is active because it is included in the plan, active on a trial basis, or requires a plan change — and toggle the ones under their control.

A custom domains page lets organizers bind their own domain to the project's public-facing surfaces, alongside domain verification and DNS diagnostics, so a tournament program can run under its own web address instead of the default platform domain.

Project Lifecycle

Projects move through their own lifecycle independent of the tournaments inside them:

• Active projects appear in the main active-projects list and are fully operational.
• Archiving a project moves it out of daily view while preserving its history and data.
• Restoring an archived project brings it back to active status.

Dedicated active and archived project list pages let organizers separate day-to-day work from programs that have wrapped up, without deleting anything.

Circuits And Long-Term Programs

Projects can also act as the home for circuit programs. A circuit can connect multiple tournaments into a larger seasonal or ranked structure.

Common circuit responsibilities include:

• creating and editing circuit records,
• managing seasons,
• associating tournaments,
• handling sponsor relationships,
• supporting cumulative standings and qualification logic.

Communications And Financial Hubs

Projects are also the scope for two important cross-cutting operating areas:

• communication hubs, where organizers coordinate campaigns, audiences, templates, deliveries, and analytics,
• financial views, where organizers review revenue, transactions, payout status, blockers, and billing state.

This is important because it means communication and finance are treated as part of program operations, not as separate systems.

Typical Project Workflow

An organizer usually uses a project in this order:

1. Create the project and define the program identity.
2. Configure appearance, billing, and team access.
3. Launch one or more tournaments inside the project.
4. Use the project dashboard to track activity across those tournaments.
5. Use project-level communications, financials, and circuits to operate the program over time.

Related pages:

• Tournament Creation, Settings, and Structures
• Governance, Support, Integrations, and Organization Controls