Introduction
Collaborators are one of the most powerful concepts in BackOps. They are the foundation of how collaboration, coordination, and real-time work happen inside an event.
Events are never created by a single person or even a single team. They are the result of many groups working together toward a shared outcome. Collaborators exist to accurately represent that reality.
At a high level, collaborators answer the question:
Who are all the groups we are working with to make this event happen?
What a Collaborator Represents
Section titled “What a Collaborator Represents”A collaborator represents a group of people, not an individual role.
In most cases, collaborators map to companies, organizations, departments, or teams that are involved in an event. Even when a collaborator appears to represent a single person (such as an artist or speaker), it is still modeled as a group, since those individuals typically have teams working with them.
Examples of collaborators include:
- Internal departments within your company
- Production vendors
- Catering, power, tent, or logistics vendors
- Venues
- Clients
- Artists or talent teams
- Speakers and their support teams
Each collaborator can contain individual people, referred to as crew, which are covered in a later section.
Flexible by Design
Section titled “Flexible by Design”Collaborators are intentionally flexible and are not constrained to predefined roles like “vendor,” “speaker,” or “artist.”
In real-world event workflows:
- A vendor may also be a speaker
- A single company may provide multiple services
- An artist may also act as a client or stakeholder
- Internal teams may be broken into departments for large events
Rigid role-based systems struggle to represent these overlaps.
By modeling collaborators as flexible groups rather than fixed roles, BackOps can support a wide variety of event types and organizational structures without forcing artificial distinctions.
Collaborators at Different Scales
Section titled “Collaborators at Different Scales”How you use collaborators may vary based on the size and complexity of your event.
For large events, you might:
- Create collaborators for each internal department
- Create separate collaborators for every external vendor
- Represent clients, artists, and partners as their own collaborators
For smaller events, you might:
- Use fewer collaborators
- Group responsibilities more broadly
- Still represent key external partners as collaborators
There is no single correct way to structure collaborators. The goal is to model the real groups involved in the event in a way that makes collaboration and delegation clear.
Collaborators as the Collaboration Engine
Section titled “Collaborators as the Collaboration Engine”Collaborators are central to how people are brought into an event and how work is shared.
Through collaborators, you can:
- Assign tasks to the appropriate groups
- Include collaborators on schedules as required or optional participants
- Share files and documentation
- Delegate responsibilities clearly
This is what transforms BackOps from a static planning tool into a collaborative, real-time operating system for events.
Without collaborators, an event is just a personal planning space. With collaborators, it becomes a shared environment where teams can actively work together.
Visibility and Control
Section titled “Visibility and Control”Collaborators also play a key role in controlling visibility.
Not every group needs access to every detail of an event. Collaborators provide a structured way to:
- Invite external teams into the system
- Ensure they see the information relevant to their work
- Keep other details scoped appropriately
While permissions are covered in more detail later, collaborators form the foundation that makes controlled access possible.
Delegation and Accountability
Section titled “Delegation and Accountability”Because collaborators represent real-world groups, they are a natural unit for delegation.
You can assign work to collaborators, track progress, and collect information from the teams responsible for specific parts of the event. This allows work to be distributed without losing oversight or control.
Collaborators enable you to bring people into your event, give them what they need, and let them contribute effectively—all within a single, structured environment.
Collaborators as a Core Concept
Section titled “Collaborators as a Core Concept”At their core, collaborators exist to reflect how events are actually produced: by many groups working together.
By modeling those groups directly, BackOps provides a flexible, scalable system that supports everything from small, simple events to large, multi-team productions—without changing the underlying structure.