Teams and workspaces
Shared workspaces, seats, brand settings, and how to roll the product out to a team without everyone reinventing the same layout.
Organizations and workspaces
An organization owns a shared workspace. Projects created in it belong to the team rather than to whoever made them, which means work survives people changing roles or leaving.
Members switch between their personal space and any organization they belong to with the workspace switcher. Keeping client or department work in separate organizations is a reasonable way to keep things tidy.
Seats and invitations
Invite members by email from the organization's settings. Each member occupies a seat, and the seat count is adjustable as the team grows or shrinks.
Seats also determine the shared AI credit pool — 15,000 credits per seat, pooled across everyone. See narration and AI credits.
Brand settings
Brand settings hold your palette, fonts, and logo at the workspace level, so every project starts consistent instead of each person approximating the brand from memory.
For a team rollout this is the highest-value thing to set up on day one. Configure branding before training people, and their first projects come out on-brand without anyone having to police it afterwards.
Working as a team
The pattern that works: build one project properly, agree it is the house style, and have everyone clone it rather than start blank. Cloning preserves layout, styling, and layer structure — only the data changes.
This matters most for recurring work. A monthly report costs real effort once and very little every month after, because the second month is the first month's project with new rows in the spreadsheet.
Projects save continuously. Two people editing the same project simultaneously is not recommended — the last write wins — so split work by project rather than by layer.
Frequently Asked Questions
Can we move existing personal projects into a team workspace?
Yes. Projects can be moved into an organization, which is the usual first step when a team formalises work that started as one person's experiment.
What happens to a member's projects when they leave?
Projects created inside the organization belong to the organization, so they stay. This is the main reason to do team work in a shared workspace rather than in personal accounts.
How should we train a new team member?
Have them open a finished house-style project, clone it, and swap in their own data. Reading documentation cold is much less effective than taking apart something that already works.
Does everyone need their own login?
Yes, each member has their own account and occupies a seat. Shared logins are not recommended, since continuous saving means concurrent edits from one account will overwrite each other.
Start Building
Free to start. No install. Import a spreadsheet and export a share-ready video in minutes.