How BackOps Fits Together: Organizations and Events

Everything in BackOps lives inside an organization, and the work of a single show lives inside an event that belongs to that organization. Once you know what sits at each level and how records move between them, the rest of the platform reads clearly.

The organization

An organization is your company's workspace. It holds the things that outlast any one show:

• Your events, listed on the organization's Events page.
• Libraries you reuse: the crew database, the collaborator database, inventory, event templates and event types.
• Org-level structure such as departments and locations.
• Members, licenses and billing.

Organization roll-ups read across every active event, so the organization Schedule, Tasks, Procurements and Orders pages show work from all of your shows in one place. A person can belong to several organizations and switch between them from the rail on the far left of the app.

The event

An event is the workspace for one production, show or engagement, and it can span any number of days. Inside it you will find:

• Collaborators: the companies and groups working the event, and the crew inside each one.
• Areas: the stages, rooms and zones the event is divided into.
• The Schedule of activities, with a run of show for any activity that needs one.
• Project Management: tasks, phases and constraints.
• Advances: structured requests for information sent to collaborators.
• Files, Dynamic Docs, procurement and event email.

An event can have an event type that decides what it collects and tracks, and it can be built from a template so a new show starts with its collaborators, areas, tasks and more already in place.

How records move between the two

The organization holds the reusable record; the event holds a working copy.

flowchart LR
  subgraph Organization
    CD[Crew database]
    COL[Collaborator database]
    TPL[Templates and event types]
  end
  subgraph Event
    EC[Event crew]
    ECOL[Event collaborators]
    STR[Event structure]
  end
  CD -- Pull from org --> EC
  EC -- Push to org --> CD
  COL -- Pull from org --> ECOL
  ECOL -- Push to org --> COL
  TPL -- Builds --> STR

When you pull a crew member or collaborator from the organization onto an event, the event gets an independent copy that remembers where it came from. Editing the event copy does not change the organization record, and the reverse is also true, until you choose to push changes back up. That link is what lets you see every event a vendor has worked, while each show keeps the details that are true for that show.

Access works at each level

Organization permissions and event permissions are separate. What someone can do inside an event comes from their event permissions, not their organization role, and inside an event access can be narrowed further to a collaborator or an area. A licensed BackOps Pro seat holder can create events; licenses decide what a person can reach, and permissions decide what they can do there.