Post-production / 2026-10-28
Before your small team shares a Resolve project, agree these responsibilities first
A preflight checklist for small post teams adopting DaVinci Resolve's Blackmagic Cloud collaboration, drawn from Blackmagic's own collaboration and tech-spec pages, covering who owns the library, how changes are accepted, and what to confirm before inviting collaborators.
Small post teams adopting DaVinci Resolve's shared-project workflow often focus on the headline promise -- several artists on one timeline at once -- and skip the quieter decisions that keep that collaboration from turning into confusion. Blackmagic's own collaboration documentation describes a specific mechanism for working together, and reading how it actually behaves points to a short list of responsibilities worth agreeing before anyone invites a collaborator.
Start with library ownership. Per Blackmagic's collaboration page, cloud collaboration runs through a Blackmagic Cloud ID and a project library created on the DaVinci Resolve Project Server, with the library hosted on a server region you choose. Someone on the team has to own creating that ID and library, pick the server, and decide who is invited. Name that person explicitly rather than assuming it, because the library owner controls the shared space every collaborator joins.
Agree how changes get accepted. The documentation states that when collaborators make changes, those changes appear in the viewer and are only applied when you accept the update, and that a single click can relink files, update timelines, or view changes. That means each editor decides when to pull in others' work. A team should agree a simple convention -- who accepts changes to the master timeline, and when -- so two people don't unknowingly diverge from the same starting point.
Decide who holds the master timeline. Blackmagic describes built-in timeline compare tools that let you merge changes into a master timeline while others continue editing. For a small team this works best when one timeline is treated as canonical and one person is responsible for merging into it, rather than several editors each believing their own cut is the authoritative one. Write that down before the project starts.
Confirm every collaborator can actually run a compatible build. Blackmagic's tech-spec page lists supported operating systems -- recent macOS releases, Windows 10 Creators Update and Windows 11, and Rocky Linux 8.6 for the relevant hardware and software. A preflight check should confirm each collaborator is on a supported OS and the same Resolve version, since a shared project is only as reliable as its least-compatible participant. Mismatched versions are a predictable source of handoff friction.
Separate the free and paid pieces honestly. The collaboration page says creating a Blackmagic Cloud ID is free, and the tech-spec page shows DaVinci Resolve Studio as a paid product. Cloud collaboration, a free Resolve ID, and a paid Studio license are distinct line items; a team should confirm which collaborators need Studio for the features they'll use rather than assuming the free download covers every workflow. This article does not independently verify current pricing -- check the exact Blackmagic store and licensing pages before budgeting.
For anything beyond a handful of people, note the Organizations option. Blackmagic documents an Organizations app that lets larger companies define groups or teams to share projects quickly. A two- or three-person team may not need it, but if your roster is growing it is worth deciding early whether you manage access per project or through an organization structure, because migrating access conventions later is more disruptive than choosing them up front.
None of this replaces a real test. These checks are drawn from Blackmagic's own documentation describing how its collaboration tools are intended to work, not from independent hands-on testing, and the exact behavior can vary by version, hardware and network. Before committing a paying client's project to a shared library, run a short rehearsal: invite one collaborator, make and accept a change, relink a file, and confirm the master-timeline merge behaves as your team expects.
Share this story: Share on LinkedIn