Shared workspaces keep projects, assets, settings, and members in one access boundary. Use them when a project needs more than one person or reusable team material.
Roles
Workspace owners and admins can manage members and settings. Members can contribute to workspace projects and assets according to their role.
Use the smallest role that fits the work. Give admin access only to people who need member, billing, or workspace configuration control.
Invites
Invite collaborators from workspace settings. Invite links are tied to the workspace, so recipients join the right account context instead of creating disconnected personal projects.
Seats and billing
Team billing is seat-based. The Team plan includes 3 editor seats; extra editor seats are billed per seat and add to the workspace’s pooled monthly Flares and standard cloud render allowance.
Billing, Flares, storage, assets, and render allowances belong to the workspace, not to an individual user. Keep the member list aligned with the people who should be able to edit production work, especially before renewal or after a client handoff.
Handoffs
Before handing off a project, make sure the important layers are named, source assets are in the workspace library, and the intended export frame is clear.
For motion work, leave the timeline in a readable state: avoid hidden timing surprises, keep final frames named, and export a quick review pass when possible.
Shared actions
Workspace-shared layer actions help teams reuse prompt operations and editing shortcuts. Keep shared actions focused, named clearly, and tested on a temporary layer before relying on them in production work.