Introduction
An overview of how licensing works in BackOps — the two levels of licenses and how they work together.
BackOps has two distinct levels of licensing: organization licenses and event licenses. Understanding how they work together is the starting point for figuring out what you need.
The Two Levels
Organization licenses control access to the shared infrastructure of a team organization — things like org-level project management, file storage, schedules, crew databases, and the roll-up views that aggregate information across all your events. These are tied to individual members of your organization. If you're in a personal organization, you don't need org licenses at all.
Event licenses control access to individual events. They work on a slot basis rather than being tied to specific people — you buy a number of seats, and those seats are available on every event you create. At least one Event Pro license is required to create any event, regardless of what other licenses you hold.
The two levels work together. Most team members hold an Org Standard license for org access, then get assigned an Event Pro slot when they need to work on a specific event. Senior people who need unrestricted visibility across all events hold Org Pro instead. External collaborators and vendors often need no license at all.
At a Glance
| License | Level | Who needs it |
|---|---|---|
| Org Standard | Organization | Anyone who needs org access — pairs with Event Pro when event access is also needed |
| Org Pro | Organization | People who need org access and unrestricted access to every event without consuming Event Pro slots |
| Event Pro | Event | Anyone working across multiple collaborators within an event; assigned as slots to org members or external people |
| Free collaborator access | Event | External collaborators, vendors, and freelancers scoped to their own collaborator |
Licenses vs. Permissions
A license determines what a user is capable of accessing — it does not determine what they are allowed to do. Those are two separate things in BackOps.
Every user in the system, regardless of license level, is subject to the permissions you assign them. Permissions control what they can see, what they can edit, and what actions they can take — at a very granular level. A user with an Event Pro license can be restricted to read-only access on every section of the event. A free collaborator can have their access narrowed further beyond the defaults. The license sets the ceiling; your permission configuration controls where they actually land within it.
This means you don't need to hesitate before giving someone a license out of concern that they'll have too much access. The license gets them in the door — your permissions decide what they can do once they're inside.
For a full breakdown of how permissions work, see the Permissions documentation.
Organization Licenses
Org Standard and Org Pro explained — who needs them and what they include.
Event Licenses
How Event Pro slots work, what free collaborator access covers, and how to figure out what you need.