Introduction

Organizations are a core collaborative structure in BackOps, but they are not the only place work can happen.

Every user has their own BackOps account, which includes a personal workspace where they can create and manage events independently. In addition to their personal workspace, users can create or join organizations, which are shared workspaces designed for team collaboration.

An organization acts as both a collaboration container and a management layer for team-based companies.

Personal Workspace vs. Organizations

Every BackOps user has their own personal workspace. This personal workspace is single-user only and is where you can:

• Manage your own license
• Create and run personal events
• Work independently without inviting others

In addition to their personal workspace, users can create or join organizations.

Organizations are multi-member workspaces designed for teams. Inside an organization, multiple users can collaborate together, share licenses, and work across events as a group. Organizations unlock team-based functionality that is not available in a personal workspace, such as inviting members and centralized management.

A user can:

• Work alone in their personal workspace
• Belong to one or more organizations
• Switch between their personal workspace and organizations based on where an event lives

What Organizations Are Used For

Organizations serve two primary purposes in BackOps:

1. Billing and Licensing

Organizations are the top-level billing unit in BackOps. All members within an organization are grouped under the same set of licenses, allowing companies to:

• Manage subscriptions in one place
• Pay for multiple users together
• Control access and scale usage as the team grows

This makes organizations the financial and administrative foundation of the platform.

2. Cross-Event Management and Roll-Ups

Organizations also act as a management layer across all events they own. BackOps provides organization-level views and tools that allow you to see what is happening across all events at once.

Examples of organization-level roll-ups include:

• Viewing all tasks across every event in the organization
• Seeing combined schedules for multiple events
• Gaining high-level operational visibility across your entire event portfolio

Additional organization-level features and roll-ups continue to be added over time, expanding the ability for teams to manage operations at scale.

Organizations and Events

Events can live in two places in BackOps:

• A user’s personal workspace (single-user)
• An organization (multi-member)

Organizations own one or more events, and those events are shared among all members of the organization. Nearly all collaborative work in BackOps happens inside organization-owned events.

At a high level, the structure looks like this:

• User
  • Personal workspace
    • Personal events
  • Organizations
    • Members
    • Shared licenses
    • Events

Inside each event is where collaborators, areas, tasks, schedules, and other operational details are managed. Personal workspaces are optimized for individual use, while organizations provide shared access, billing, and cross-event visibility for teams.