How BackOps Licensing Works: BackOps Pro, Event Pass, Org Pass
An overview of BackOps licensing, covering the BackOps Pro core seat, the Event Pass and Org Pass add-ons, free collaborator access, and how licenses differ from permissions.
Licensing in BackOps is organization-scoped: your organization holds the licenses, and seats on them go to people. Every organization has one core license, BackOps Pro, and can add two passes for people who need less than a full seat.
Why It Is Built This Way
A production company's team is not uniform. A few people plan and run every show and need to be everywhere. Others, such as a freelance stage manager, a client, or a warehouse coordinator, need working access to one event or to the organization's records, but not both. Licensing follows that shape so you pay for the access each person actually needs.
The Licenses at a Glance
| License | Who it is for | What it gives |
|---|---|---|
| BackOps Pro | People who plan and run your events | Organization access, creating events, and working access on every event in the organization without using an event seat |
| Event Pass | People who work on specific events, including freelancers and clients outside your organization | Working access on the events they are added to |
| Org Pass | People who work with the organization's records but not inside events | Organization-level pages, such as crew, collaborators, and cross-event views, without working access inside events |
| Free collaborator access | Vendors and partners invited into an event | Permissions on their own collaborator only |
Only a BackOps Pro seat holder can create events.
flowchart TD
P["BackOps Pro seat"] --> O["Organization pages"]
P --> A["Every event, no event seat used"]
P --> C["Create events"]
OP["Org Pass seat"] --> O
EP["Event Pass seat"] --> E["The events they are added to"]
F["No pass"] --> S["Their own collaborator only"]Licenses vs. Permissions
A license decides what someone is capable of reaching. Permissions decide what they are allowed to do there. A BackOps Pro seat holder can still be limited to read-only on parts of an event, and an Event Pass holder only sees what their event permissions allow. Give someone the license their role needs, then set their permissions.
Where Licensing Is Managed
Your first BackOps Pro seats are bought, or a trial started, when you create the organization. After that, organization admins manage seats, passes, payment, and invoices in Settings › Billing, and assign seats to people in Settings › Members.
BackOps Pro and Org Pass
The core seat and the organization-only pass.
Event Pass and Collaborator Access
Working access on single events, and what invitees without a pass get.
Buying, Trials, and Resuming
How a purchase or trial starts, and how to buy again after a lapse.
Managing Billing
Seats, passes, payment methods, invoices, and cancelling.
Usage Allowances
AI credits and storage that come with each BackOps Pro seat.