Guide

Workspaces and collaboration

Personal versus team workspaces, invitations, naming conventions, and how to keep AI presets aligned when multiple people ship content.

Published

Last updated

Workspaces separate who sees what: your personal space for drafts and experiments, and shared spaces for team series, research, and production handoffs. Getting boundaries right early prevents accidental shares and conflicting presets.

Personal workspace

Default private area for ideas not ready for team review. Use it for risky experiments, competitor deep dives you do not want mixed with brand channels, and scratch scripts. Promote work to a team workspace when it needs shared ownership.

  • Keep personal naming messy if you want—clarity matters more in shared spaces.

  • Archive old tests so your overview stays honest.

Team workspaces

Invite collaborators when multiple people touch scripts, research, or approvals. Agree on: canonical project names, where comments live, and which preset is default for client-facing work.

  1. Owner assigns roles aligned with real responsibilities—not everyone needs admin.

  2. Document the preset + minimum rules stack for brand work.

  3. Use consistent series prefixes so lists sort predictably.

Collaboration rituals

  • Weekly sync: what shipped, what blocked, what changed in messaging.

  • Script review: one owner per video for final voice—avoid design by committee in the draft.

  • Asset handoff: thumbnail and B-roll expectations in video notes.

Permissions and plans

Features may vary by subscription or admin policy. If you cannot access a workspace action, ask whether it is plan-limited or role-limited—fixes differ.

Misaligned presets cause “two channels in one.” Pick one team preset and iterate publicly inside the team.