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,
• upcoming activity,
• total participant volume,
• recent tournaments,
• subscription or plan status,
• quick actions into settings, team management, communications, and tournament creation.

In business terms, it acts as the project command summary rather than a deep operational workspace.

Workspace Modules

Projects expose different workspace modules depending on access and availability. In practice, this creates a modular operating environment that can show or hide areas such as:

• overview,
• tournaments,
• settings,
• team,
• wellness,
• financials,
• communication,
• circuits,
• analytics,
• marketplace-related financial views.

This matters for partners because the organizer experience is not flat. It can be shaped by plan level, project state, and role permissions.

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.

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