Transferring Projects
Move a personal project into one of your workspaces, picking exactly where it lands.
Personal projects live outside any workspace — only you can see them, and only people you've shared them with directly. When the work is ready for a team, transferring brings the project into a workspace you belong to and drops it into the exact spot you choose.
This page covers how to transfer, where projects can land, what changes after the move, and who is allowed to transfer where.
How to Transfer
Open the project's menu
On the home page in your Personal context, right-click the project card (or open the … menu) and pick Transfer to workspace….
The menu item only appears for personal projects you created. If you're not the project's creator, or you're already in a workspace context, the option is omitted.
Pick a workspace
The dialog shows a Workspace picker listing every workspace you belong to. Choose the one you want the project to move to.
If you aren't a member of any workspace yet, Fuser tells you to create one first — there's nowhere to transfer to until then.
Pick a destination inside the workspace
Below the picker, a tree shows the places you can drop the project. Workspaces with a single team auto-expand so you can see its folders without an extra click.
You can land the project in one of four places — see Where Projects Can Land below.
Confirm
A summary appears once both a workspace and a destination are selected: where the project is going, what its new visibility will be, and a reminder that personal collaborators will lose access. Click Transfer to commit, or Cancel to back out.
On success, Fuser shows a toast with a View link that opens the project in its new workspace context.
Try the Destination Picker
Click and expand below to see how the picker behaves in the real dialog. Picking the workspace targets the workspace root; expanding it reveals workspace folders. Each team is its own expandable row with its folders inside.
Where Projects Can Land
You pick exactly one of four destinations inside the workspace:
| Destination | Where it lives | Notes |
|---|---|---|
| Workspace root | The top level of the workspace, outside any folder or team. | Visible to every workspace member, governed by the workspace root's default access. |
| Workspace folder | A folder that belongs to the workspace itself, not to a team. | Anyone who can see the folder can find the project. |
| Team | The root of a specific team. | Only that team's members can see the project. |
| Team folder | A folder inside a team. | Gated by team membership, then by the folder's own default access. |
For the full rules on what each destination's defaults mean, see Folders and Access Reference.
What Changes When You Transfer
- Visibility resets to the workspace default. The project is set to Draft or Published based on the destination workspace's setting, regardless of what it was before. The dialog shows you the new value before you confirm. Change it later in Workspace Settings → Access Defaults.
- Personal collaborators lose access. Anyone you'd shared the project with directly — by name or by email link — is removed. They won't see the project anymore. If you want them to keep access, re-invite them in the destination workspace using the project's Sharing tools after the transfer.
- Media follows the project. Images, generations, and files used in the project become visible to the destination workspace through its asset library. Anything you don't want shared, remove from the project before you transfer.
- The project keeps its history. The flow, comments, and version history move with the project unchanged.
- An entry appears in the workspace activity log. Workspace Admins can see who transferred what, when, and where it landed.
Who Can Transfer Where
A few rules decide whether a destination is available:
- You can only transfer projects you created. You won't see the menu item on someone else's personal project.
- You must be a member of the destination workspace.
- Owners and Admins can transfer to any destination in the workspace.
- Members can transfer to the workspace root, to any workspace folder they have edit access to, to a team they belong to, or to a folder inside a team they belong to (provided they can edit that folder).
Destinations you can't reach are filtered out of the tree, so the dialog only shows you valid choices. For the precise edit-access rules, see Access Reference.
One-Way and Irreversible
Transfers can't be undone
Once a project is transferred, it belongs to the workspace. There is no built-in transfer back to personal — if you want a personal copy of the work, duplicate the project before or after the transfer. Personal collaborators don't auto-restore either, so make a list before you confirm if you intend to re-invite them.