Team Collaboration

Run a Studio, not a Slack channel. If you’re operating more than one faceless channel, or running client work as an agency, the Studio needs structure: workspaces per channel, clear roles, and an approval flow that gets to render without a thread of “can you check this?” messages.

This guide is for multi-channel solo operators and agency teams deciding how to set up CreatorStudio for ops-level use.

Pick the right tier

Two tiers are built for team shapes.

• Pro ($100 / month). For multi-channel operators and small agencies. Includes multi-channel workspaces and priority render queue on top of everything in Creator. Right if you run two to five channels solo, or run a two-to-three-person team shipping for a handful of clients.
• Power / Studio ($500 / month). For agencies, labels, brand teams, media companies, and marketing plus design teams. Adds 24x7 autonomous streams, brand-kit API, and seat licensing on top of Pro. Light demo, one-to-two week close cycle. Right if you run more than five channels, operate as an agency with named client accounts, or need autonomous streams (the Aditya Music and Aditya Bhakthi shape).

There’s no enterprise RFP dance. Power tier is self-serve with a light demo. No per-seat custom pricing, no four-month procurement cycle.

Workspaces

The right mental model: one workspace per channel or per client.

Each workspace has its own Director Memory Graph. That is load-bearing. The Graph is the compounding dataset for that channel’s voice, visual fingerprint, audience signal, and conversion patterns. You do not want a history-channel workspace and a finance-channel workspace sharing a Graph; the signals will pollute each other. Keep them separate.

For agencies: one workspace per client. The brand kit, Memory Graph, render history, and approvals stay scoped to that client. When the client offboards, the workspace goes with them cleanly.

Roles

Roles depend on tier.

• Pro supports a lighter approval flow suited to a small team. Think of it as a Director (whoever briefs Ra and hits render) and reviewers with approval access. The shape is informal; the important thing is that only the Director owns the render decision.
• Power supports seat licensing and is the right shape when you need named seats, auditable approval, and formal separation between who drafts, who approves, and who can only view. Treat Power as the tier that supports agency and studio ops, where “who approved this” is a question someone might need to answer.

Where CreatorStudio doesn’t specify a named role in your tier, the operating rule is the same: only one person owns the render decision per story. That role is the Director.

Review and approval flow

The loop is the same at every tier:

1. Director drafts. Paste the logline, let Ra generate the Director Brief, iterate on the Brief until the storyboard is locked. Still free at this stage, no render cost yet.
2. Reviewer approves. Whoever owns brand or client-side approval reviews the Brief. Approvals happen on the static storyboard plus script, before any render spend. This is the right place to catch drift: static is cheap, rendered video is not.
3. Render. Director hits render. Ra routes the models, delivers in about fifteen minutes. Approval from step 2 is what unlocks render.
4. Publish or queue. The rendered story goes to the Publishing module, scheduled or shipped immediately.

Keeping approval on the Brief, not the render, is how you keep the render queue efficient and the approval cycle cheap.

Brand kit and Memory sharing across workspaces

Each workspace has its own Memory Graph. That is intentional. What doesn’t automatically share across workspaces:

• Brand kits
• Character casts
• Voice profiles
• Conversion signals

For an agency, this is the right default: Client A’s brand kit should not leak into Client B’s Graph. For a multi-channel operator running brand-adjacent channels, upload the shared brand kit into each workspace where it applies.

Power tier supports a brand-kit API, which is the right shape if your design system is version-controlled or your brand kit needs to stay in sync across many workspaces from a single source of truth.

Best practices for agency operators

A few patterns that tend to hold:

• Spin up a client workspace on day one, before any render. Paste their URL, upload their brand kit, let Ra build the Graph. Validate the Graph with the client before the first Brief. This turns onboarding into a shared artefact instead of a kick-off call.
• Name your workspaces by client, not by project. Client-level workspaces keep the Graph compounding across every project you run for them. Project-level workspaces fracture the Graph and reset Memory every time.
• Keep a Director per client. Even if multiple people touch the account, one Director owns render. Avoids approval loops.
• Approve on Briefs, not renders. Render is where the cost lives. Static Briefs are where catch-and-correct is cheap.
• Use the badge. Every paid render on Power (and Creator and Pro) carries the “Made with CreatorStudio” badge by default. Leave it on unless a client specifically opts out. At agency volume the badge is free distribution, which is how your next client finds you.
• Review the Memory Graph every quarter per client. Audience signal, conversion patterns, and format DNA drift. A quarterly Graph review with the client is a good renewal conversation and a cheap way to catch positioning drift before it shows up in render.

CreatorStudio is infrastructure, not agency labor. The Studio does what it does; your team’s job is to direct it well.