Docs

Organizations in BackOps: Your Team's Shared Workspace

What an organization is in BackOps, how it holds your events, crew, and licenses, and how members, permissions, and cross-event views fit together.

An organization is your company's workspace in BackOps: the container that holds your events, your crew and collaborator databases, your inventory, your templates, your files, and the licenses that pay for it all. Everything you do in BackOps happens inside an organization, and a solo producer is simply a one-person organization.

Why Organizations Matter

A production company does not run one show. It runs dozens, with the same people, the same vendors, the same gear, and the same venues appearing again and again. If each event stood alone, every show would start from a blank page and nobody could see the whole calendar at once.

The organization is what lets your company's knowledge carry from one event to the next. Crew, collaborators, resource types, and templates live at the organization level and are pulled into each event. Organization-level views read across events, so you can see every task, activity, procurement, and order in one place.

How Organizations Work

One organization, many events. An organization owns its events. Being a member of the organization does not by itself open every event: access to an event comes from that event's own permissions, which organization admins can manage.

Members and permissions. A member is a person with an account, a license seat, and organization permissions. Organization permissions decide what someone can do at the organization level. What they can do inside an event comes from their event permissions. The person who creates the organization becomes its first organization admin.

Licenses. Licenses belong to the organization. Every organization holds a BackOps Pro license, and seats on it go to the people who plan and run your events. See Licensing.

Cross-event views. The organization Schedule, Tasks, Procurements, and Orders pages read across the organization's active events, alongside the organization's own schedules and tasks. Archived events drop out of them.

flowchart TD
    O["Organization"] --> M["Members and permissions"]
    O --> L["Licenses and billing"]
    O --> DB["Crew, collaborators, inventory, templates"]
    O --> E["Events"]
    DB -->|"pulled into"| E
    E -->|"roll up to"| V["Org Schedule, Tasks, Procurements, Orders"]

You can belong to several organizations, for example your own company and a client's that brought you in as crew. Each one appears on the left rail. If you are invited only to an event and belong to no organization, you still reach that event from Home.