Hand off a project to a collaborator

Uses

By the end of this guide a colleague will be able to open and edit a project you have been working on.

Titan does not currently produce a “packaged project” file that you can email. Instead, handoff means either (a) sharing the project so it lives on the server and both of you edit it live, or (b) putting the project’s folder somewhere your colleague can reach it and having them open the folder in their own Titan. The two paths trade off real-time co-editing against working asynchronously.

Prerequisites

The project you want to hand off, already open in Titan.
Decide which path you want before you start. The decision below covers most cases.

If you want…	Use
Real-time editing with the other person (both of you in the project at once, cursors visible)	Share path
The other person to work on their own, possibly offline, possibly modify the structure	Folder path
To keep the original on your machine and send a snapshot	Folder path
The other person to have ongoing access without you sending updates	Share path
To hand off to someone outside your account (no Titan login required)	Folder path

If you are unsure, the share path is the lower-friction default. The folder path is for cases where you specifically want a copy rather than a live connection.

[Asset: annotated screenshot] One screenshot of the share dialog with role selection and copy-link control highlighted. Asset name: handoff-share-dialog.png. Replaces no existing placeholders.

1. Confirm the project is not already shared

In the header, the storage icon shows whether the project is Private or Published (with private backing details). If it shows the published/cloud state, the project has already been shared and you just need to invite a new collaborator. Skip to step 3.

Click Share in the header.

If the project is private (browser-backed or folder-backed), sharing creates a server copy. The original local copy stays on your machine and the two are kept in sync from now on. You will see the storage icon change from private to published after a moment.

3. Invite the collaborator

In the share dialog:

Enter the collaborator’s email.
Pick a role. Editor lets them change content; View only lets them read.
Send the invite.

If the dialog also offers a copy-link option, you can share the link directly instead of inviting by email.

4. Confirm they can open it

Ask your collaborator to open Titan in their browser, sign in, and look for the project in their dashboard or open the link you sent.

When they have it open, the status bar should show Synced on both sides. If you both edit at the same time, you should see each other’s cursors.

Steps: folder path

1. Get the project onto disk

If the project is already private and folder-backed (the header shows a folder-backed private state), skip to step 2.

If the project is private and browser-backed, you need to write it to disk first. From the project dropdown or storage menu, use Save to Folder (or Open Folder if creating a fresh local folder for it). Grant the folder permission when prompted. Titan writes the project’s files into the folder.

2. Put the folder where your collaborator can reach it

Pick a transfer mechanism. Anything that moves a folder of files works:

Sync tool you already use: Dropbox, iCloud Drive, OneDrive, Google Drive (treated as a regular folder, not a Titan integration).
Git: initialise the folder as a repo and push.
One-time copy: zip it and send it.

Titan does not control the transfer. It only cares that the destination ends up as a folder on the collaborator’s machine.

3. Have the collaborator open the folder in their Titan

The collaborator opens Titan in a Chromium browser, clicks Open from computer → Open folder, and picks the folder they received. Their Titan reads the files and creates a local project against them.

From this point each collaborator has their own local copy. Edits do not propagate between you. If you both edit the same file, the sync tool (or git) will produce conflicts that you resolve outside Titan.

Verification

Share path is working if:

The header storage icon shows the cloud glyph on your side.
The status bar shows Synced when you and the collaborator both have the project open.
An edit you make appears in the collaborator’s editor within a couple of seconds.

Folder path is working if:

The collaborator can open the folder in their Titan and see all your files in the explorer.
They can open one file and make an edit that saves to disk.
Your sync tool propagates that edit back to your machine (or, for git, after they push and you pull).

Variations

Share path with role-mixing. Some collaborators as Editor, others as View only. Useful when the second group is just reviewing.
Folder path with read-only intent. Send a zip and tell the recipient they are not expected to push changes back. The simplest handoff there is.
Hybrid. Share the live project and also send a zip of the current state as a snapshot. The snapshot is the version you will reference in a paper or report; the live project is where work continues.

If something goes wrong

The Share button is not visible. You are not signed in. Sign in from the account menu in the header.
The status bar shows “Connecting…” for a long time. Network or auth issue. See Real-time collaboration for the troubleshooting checklist.
The collaborator opens the share link and sees no content. Either the share has not propagated yet (wait a minute and retry) or their role is View only and they expected to edit (re-invite them with Editor).
Open folder is greyed out in the collaborator’s browser. They are on Firefox or Safari. Open folder needs the File System Access API, which only Chromium-based browsers support. Use the share path instead, or have them sync the folder into browser storage with Import files.
Folder-path edits are not propagating. That is expected. Folder-path collaborators each have their own copy; propagation is your sync tool’s job, not Titan’s.