Project ownership
Transfer a project to another team member. The right tool when the original creator is leaving the team or handing off the lead.
Each project has an owner – the team member it was authored by, or whoever the project has been transferred to. Project ownership controls who's the canonical maintainer; transfers happen when the original owner is no longer the right person to hold it.
What it does
A project's owner has a few specific responsibilities and capabilities:
The project carries the owner's identity in the project metadata.
When a member is removed from the team, their owned projects need to be transferred or they remain orphaned.
Transferring ownership reassigns the project to another team member. The current owner becomes a regular team member on that project; the new owner takes the canonical maintainer slot.
How owner privileges relate to team-member access
Owner is a metadata label on the project plus team-management authority, not a per-project edit override. The relevant scopes:
Members with full access can edit and manage projects in the team area, including projects they don't own.
Owners carry additional team-level capabilities such as editing the permissions of team members.
Read-only members can view projects but cannot make changes to them. Whether read-only members can publish a project from the Share dialog is unconfirmed; ask the team if this matters for your workflow.
How to transfer
From the homepage or project listing, find the project.
Open the project's More menu (three-dot icon on the card).
Click Transfer ownership.
Pick the recipient from the team's member list.
Confirm.
The transfer is immediate. The recipient sees the project under their owned-projects view (if such a view exists in the homepage filter); the previous owner sees the project as still accessible but no longer marked as theirs.
When to transfer
A team member is leaving. Transfer their owned projects to whoever's picking up the work.
A handoff between leads. The original creative lead has moved on; transfer to the new lead.
An archive scenario. Transfer to a designated "archive" account so the original owner can be removed without orphaning the project.
A client-engagement closeout. Transfer to the agency's principal so the project stays accessible after the project lead's contract ends.
Limits and known issues
Transfer doesn't change credit attribution for past renders. Renders the previous owner produced still count against whatever credit balance was active at render time. The transfer affects future authority, not historical billing.
Cross-team transfers aren't supported. A project owned in Team A can't be transferred to Team B's member – the recipient must be in the same team. To move a project across teams, recreate or use export workflows.
Personal-to-team transfer isn't supported. A project authored in your personal workspace can't be transferred into a team workspace today. If a project needs to move to a team, recreate it there.
Related
Sharing and collaboration – how non-owner team members access a project.
Plans and billing – the billing context an owner answers for.
Account and settings – avatar menu and where the current owner shows up.
Last updated
Was this helpful?