How to Set Up a Persistent Video Workspace for a Post Facility

Why do setup decisions matter more than the product?

Because a facility that skips straight to configuration inherits the platform’s defaults as its operating model, then spends the first quarter finding out those defaults assume a different kind of business. Post makes this sharper in two ways. Most participants are external: editorial, visual effects, color and sound vendors, freelancers and client-side executives. And the work runs into evenings and weekends, so anything designed around office hours fails on the first late review.

This guide picks up after selection. For choosing a platform, see our guide to shortlisting persistent video platforms for post.

Start with a session inventory

List every recurring session type: dailies, editorial review, visual effects review, color sessions and client screenings. For each, note typical attendance, length, frequency, the hours it runs, how many sources it shows at once, whether it’s directed or passive, and what material is viewed. A directed session with a colorist and a passive dailies screening need different things, and one setup built for both will overserve one and underserve the other.

This inventory drives everything below: room structure, roles, capacity and support.

How should rooms map to shows and stages?

One arrangement fails predictably: a general-purpose room reused across shows. Access has to be reset constantly, and eventually someone sees material from a production they aren’t on. Two arrangements work.

Whichever you choose, set a naming convention before creating the first room. Once there are more than about a dozen, names become the main way people find the right room, and a convention retrofitted later is rarely applied properly.

How should roles and access work?

Design around outsiders, since they’re the majority. Vendors, freelancers and client-side viewers should be first-class cases in the model, not exceptions to an internal scheme.

Use at least three roles. Administrators configure everything; session hosts can run a review and admit people within limits; viewers attend without changing anything. Facilities with only administrators and viewers end up handing admin rights to people who just need to start a session.

For large vendor organizations, ask about federation. NIST describes it as letting a credential service provider supply authentication attributes to many separately administered relying parties, with users signing in through their own organization.¹ That lets a 200-person VFX house be connected, and later disconnected, as a unit. Our guide to browser-first collaboration covers sign-on in more detail.

Write down revocation, because it’s the half that decays: who removes access, on what trigger, and how often participant lists are reviewed. Ask whether the platform can remove a whole vendor company in one action. If it can’t, keep a list of each vendor’s people and the rooms they’re in, so removal at wrap is a checklist, not a memory exercise.

How does it connect to the facility signal chain?

Be clear about where the workspace sits. In a facility built on SMPTE ST 2110, the suite that carries, synchronizes and describes separate video, audio and data streams over managed IP networks,² an internet review platform is a boundary device, not part of that managed environment.

Specify the source for each session type. Dailies may come from file uploads, an editorial session from a bay’s output, and a video village from several live camera feeds. Each implies a different capture and encoding setup.

Decide where encoding happens and who owns it. A software encoder on a workstation shares that machine’s fate; a dedicated encoder is a known quantity with its own power, space and upkeep. Facilities running frequent sessions usually benefit from dedicated hardware. Then document the network path end to end, including the domains and ports the platform needs and where inspection or filtering sits. It’s the item most often missing from a plan and most often behind a failed first session.

How should capacity and storage be planned?

Plan upload per concurrent session, not per facility, and plan for the peak: the evening when three reviews run at once while renders and transfers are already using the line. A facility provisioned for ingest and delivery can find its upload stretched once several live sessions overlap. Test that evening before rollout, so a capacity problem isn’t misdiagnosed as a platform problem.

Separate active storage from retention. Ask whether material kept after wrap is priced differently from material in active rooms, because paying active rates for an archive is a quiet, lasting cost.

Set retention and deletion from production requirements, not convenience. On protected work, those usually trace back to the MPA Content Security Best Practices maintained by the Trusted Partner Network,³ and they should shape the retention plan from the start.

What does a realistic rollout look like?

Expand by session type, not headcount. Facilities that add people to an unchanged structure usually find the structure was only ever right for the first case.

Who runs it day to day?

Someone will absorb this work whether or not it’s assigned, and it usually lands on assistant editors and post coordinators. Name the role, and count all of the work:

Facilities that count only the per-session work consistently underestimate. Ask the vendor who is reachable during your evening and weekend sessions, and decide internally who can grant emergency access without waking a systems administrator. Put the operating time in the business case too: saving twenty minutes of setup across four sessions a night is a real return, and adding ten minutes is a cost however good the review itself looks.

What goes wrong in the first ninety days?

• Access requests outrun the process. If onboarding a vendor takes longer than the schedule allows, work moves to whatever channel is available now, and you lose both control and the benefit.
• Rooms drift. Rooms created in a rush pile up outside the naming convention, and within three months nobody knows which is current. A monthly structure review in the first quarter prevents most of it.
• Peaks are underestimated. A setup sized for a typical session meets its first busy evening and the platform gets blamed for a capacity plan.
• Housekeeping is nobody’s job. No one is scheduled to remove departed freelancers, close finished rooms or archive completed shows. Attach these to existing rhythms such as wrap and the weekly production meeting.

Coresee makes a persistent, browser-based video collaboration workspace, the kind of platform this guide describes setting up.

Published November 9, 2026