Agencies

Client video kept separate, and handed over cleanly

An agency needs each client’s video organised under the right player settings, accessible to the right team and documented for handoff. A project provides that working boundary; confirm separate client workspace, approval and billing requirements before they enter the statement of work.

Start free trialTalk to us

One project per client, handed over cleanly

The problem

How agency video estates get messy

Work starts on whatever the client already had, or on a personal account somebody set up for one campaign. Three clients later there are four logins, two of which belong to a producer who has left, and nobody is sure which brand’s settings are on which video.

The consequence arrives at handover. A client asks for their video assets and the honest answer is that they are scattered, some are in an account the agency cannot transfer, and reproducing the player configuration means somebody remembering what it was.

One account with a project per client fixes the organisation problem. A deliberate handover document then fixes the ownership problem by recording the assets, settings, embed locations and responsible account.

The workflow

Running several clients from one account

  1. 01

    One project per client

    Projects separate content and settings, so each client’s videos carry their own player configuration and protection mode. This is also the boundary you will hand over later, so set it up per client from the start rather than per campaign.

  2. 02

    Configure and embed per brand

    Set player colours and controls to the client’s brand and embed on the client’s pages. Logo and brand-text controls are entitlement-dependent, so confirm what your plan covers before quoting a fully branded player.

  3. 03

    Scope who on your team can touch what

    Manager access can be project-scoped, so a freelancer working on one client does not get the run of every account. Review this when people join and when they leave.

  4. 04

    Provision from your own onboarding

    Projects and their settings are addressable through the API, so a new client can be set up by your own process rather than by somebody clicking through a dashboard from memory.

  5. 05

    Hand over documented assets and settings

    At the end of an engagement, give the client the video list, the project’s player and protection settings, the embed locations and the domain restrictions in writing. Treat this as a deliverable — it is the part that makes you easy to work with and easy to leave.

The mechanisms

What projects actually give you

Content and settings separationPer project
Each project holds its own videos, player configuration and protection mode. This is the real basis for running several brands without them bleeding into each other.
Project-scoped manager accessTeam
Access for the people on your team can be limited to particular projects, which is the control that matters when contractors rotate.
Player configuration per brandPer project
Appearance and behaviour options set per project; logo and brand-text controls are entitlement-dependent.
API provisioningAutomation
Projects, videos and access are addressable through the current public API, so onboarding a client can be a script rather than a checklist.
Aggregate reporting per projectPopulation level
Plays, watch seconds and completion, which is what a monthly client report actually needs.
Customer-identified analyticsPlus and larger plans
When the client embed supplies its own user ID, accepted playback events can support per-user viewing reports alongside aggregate project reporting.

Fit

Where this works for an agency

  • Best for — several brands, one team

    You produce and publish for multiple clients and need their video organised and branded separately without separate accounts to administer.

  • Best for — productised onboarding

    You have a repeatable client setup and want it provisioned by your own process through the API.

  • Best for — brand-sensitive deliverables

    Client-facing video that must not carry a vendor’s logo, configured per project.

  • Plan client access and approvals

    Record any requirement for a client workspace, review-and-approve flow or separate invoices, then ask us to confirm the currently supported arrangement in writing before you scope or sell it.

Set up one client project properly

Create a project, configure the player to that client’s brand, embed on their page and write down the settings. If the handover document falls out of that easily, the model works for you.

Start free trialTalk to us