Connected feature
Admin-set base instructions enforce brand voice across every team member's pipeline run.
Back to features
Feature page
Team workspaces for multi-user video production without the chaos.
Every member of your video production operation — operators, editors, reviewers, clients — gets a shared environment scoped to their role. Jobs, uploads, and settings stay isolated behind row-level security.
TL;DR: Outbox workspaces are multi-tenant by default. Create a workspace, invite your team, assign roles (owner, admin, editor, viewer), and every pipeline run, upload, and setting stays scoped. Brand voice, caption rules, and pipeline templates lock at the admin level.
4 role typesRow-level securityMulti-tenant isolationBrand-locked config
Workspace tenant
One isolated container per team.
RLS-enforced
Members(with roles)
Jobs & Pipeline Runs
Uploads & Assets
Voice Configuration(base instructions)
Pipeline Templates
Settings(description links, brand rules)
Problem
What breaks when a second person touches the pipeline?
Solo creators don't need team features. But the moment an editor, a VA, or a client who needs to approve scripts enters the picture, coordination collapses into Slack threads, shared passwords, and Google Drive links.
The daily reality
?
Who approved this script?
You check Slack threads, email, and Notion comments before giving up.
?
Which voice settings did we use last time?
Someone changed the narrator brief and nobody noticed until the video sounded wrong.
?
Can the client see the draft?
You export an MP4, upload it to Google Drive, and share a link manually.
?
Did the freelancer access the wrong project?
You shared one login across three contractors. Now Client A's footage is in Client B's folder.
Outbox approach
Collaboration is built into the pipeline — not bolted on.
One workspace per project or client.
Roles enforced at every layer.
Brand config locked by admins.
Zero data cross-contamination.
Architecture
The multi-tenant model behind workspaces
01
Sign up
Create your account with email or OAuth. A member profile is set up automatically.
02
Name your workspace
My Channel, Agency HQ, Client – Acme Corp — whatever fits your operation.
03
Get the owner role
You are the owner of your first workspace. Full control by default.
04
Run pipelines
Start production immediately. Invite collaborators later when you are ready.
Team members
Four roles. Database-enforced.
4 members
A
AlexJ
JordanS
SamC
ClientRoles
Four roles, database-enforced
Every member gets one of four roles. Permissions are enforced at the database layer — an editor can't escalate their own access, and a viewer can't start a pipeline run even by calling the API directly.
| Role | Permissions | Typical user |
|---|---|---|
| Owner | Full access — billing, members, workspace settings, pipelines, approvals. | Founder, agency principal, channel owner |
| Admin | Manage members and settings. Run pipelines. Set base instructions and templates. | Production lead, senior editor, ops manager |
| Editor | Run pipelines, upload footage, adjust per-run settings. Cannot change workspace config. | Video editor, VA, freelance operator |
| Viewer | View pipeline status, completed videos, and metadata. Cannot trigger runs. | Client, stakeholder, reviewer |
Consistency
Brand controls that don't depend on trust
The biggest risk in multi-person video production is consistency. Three editors producing for the same channel means voice tone drifts, caption styles diverge, and metadata quality varies by who ran the pipeline.
Outbox fixes this with workspace-level configuration that admins control and editors inherit.
Base Instructions
Voice guidelines, pronunciation rules, and brand constraints that apply to every pipeline run. Editors cannot override these.
Example
"Always pronounce Outbox as two words. Never use exclamation marks. Maintain a professional, measured tone."
Pipeline Templates
Reusable configurations for voice ID, speed, caption style, and metadata rules. Editors select a template and adjust only what they need.
Description Links
URLs and labels that auto-populate every video description. Channel links, socials, affiliate URLs, legal disclaimers — set once, applied everywhere.
Security
How data stays separated
Outbox does not rely on application code to keep workspaces apart. Every table is scoped to a tenant ID and protected by row-level security policies. API requests without valid workspace membership return zero rows — not an error, just empty.
| Data type | Scoped by | Who can access |
|---|---|---|
| Pipeline jobs | tenant_id | Workspace members only |
| Uploaded footage | tenant_id | Workspace members only |
| Stage run history | tenant_id | Workspace members only |
| Voice configuration | tenant_id | Admins: full control. Editors: per-run override. |
| Workspace settings | tenant_id | Owner and admin roles |
| Member profiles | Per user | Own profile only |
Comparison
Team workspaces vs. the shared-login approach
Still sharing a single login across your team? Here is what that actually costs you.
| Dimension | Shared login | Outbox Workspaces |
|---|---|---|
| Audit trail | No idea who did what | Every action tied to a member |
| Permissions | Everyone has full access | Four roles with enforced boundaries |
| Brand consistency | Hope everyone reads the Wiki | Admin-locked base instructions on every run |
| Client separation | One wrong click shows wrong data | Database-level isolation per workspace |
| Offboarding | Change the shared password and pray | Remove member. Access revoked instantly. |
| Security | Single point of compromise | Individual auth with row-level security |
Pipeline
How workspaces shape every pipeline feature
Connected feature
Review checkpoints let viewers and admins approve scripts before voiceover renders.
Connected feature
Caption style presets are set at workspace level. Consistent formatting regardless of who runs the pipeline.
Connected feature
Description links, default tags, and metadata templates are workspace-scoped.
Connected feature
Publishing credentials and channel config live at workspace level. Editors publish without managing OAuth tokens.
Connected feature
Voice presets saved to workspace are available to all editors. Brand-approved voices only.
Plans
Workspace plans that scale with you
Every workspace has a plan that determines limits and capabilities. Data isolation is enforced on all plans — security is not a premium feature.
| Capability | Free | Pro | Enterprise |
|---|---|---|---|
| Workspaces | 1 | Unlimited | Unlimited |
| Members per workspace | 1 | Up to 10 | Unlimited |
| Roles | Owner only | All four roles | All four + custom |
| Base instructions | Default only | Full customization | Full customization |
| Pipeline templates | 1 | Unlimited | Unlimited |
| Data isolation | RLS-enforced | RLS-enforced | RLS + audit log |
See full plan details on the pricing page.
Audience
Who uses team workspaces?
Agencies with multiple client channels
One workspace per client. Your production team edits. Clients get viewer access to approve output without Google Drive exports.
YouTube channel teams
Lock your voice config at the admin level. VAs trigger pipeline runs as editors without touching the settings you spent weeks dialing in.
Freelancers across client accounts
Switch between client workspaces from the dashboard. Each one has its own jobs, templates, and settings. Your personal workspace stays separate.
Course creators with review workflows
Give your subject-matter expert viewer access, enable the review checkpoint after scripting, and they approve each lesson in-platform.
Agency example
Three clients. Three workspaces. Zero data crossover.
Client – FinanceApp4 members
onyx @ 0.95xFormal, measured
Client – FitnessBrand3 members
nova @ 1.15xEnergetic, motivating
Agency Internal6 members
echo @ 1.0xTechnical, clear
FAQ
Common questions about team workspaces
Can I belong to multiple workspaces?
Yes. Your Outbox account can hold memberships in multiple workspaces with different roles in each. A workspace switcher lets you move between them.
What happens when I remove a team member?
Access is revoked immediately. They lose visibility into all jobs, uploads, and settings. Any pipeline runs they triggered remain with the workspace.
Is data shared between workspaces?
No. Each workspace is a fully isolated tenant. Jobs, uploads, voice configuration, pipeline templates, and settings are scoped exclusively to their workspace.
How do I transfer workspace ownership?
The current owner can promote an admin to owner. There must always be exactly one owner per workspace.
What's the difference between workspace settings and per-run settings?
Workspace settings (base instructions, description links, templates) are admin-controlled and apply to every run. Per-run settings (narrator brief, voice speed, footage) are controlled by whoever triggers the pipeline.
Can I use workspaces for client approval workflows?
Yes. Create a workspace per client, invite them as a viewer, and they see pipeline status and completed videos. For script approvals, enable the review checkpoint.
Get started
Raw footage in. Published video out. Now with the whole team.
Create your workspace during onboarding. Invite collaborators, lock brand voice at the admin level, and let editors run pipelines within guardrails that keep every video consistent and every client's data isolated.