Sharing and collaboration

Two ways to get someone into a project – email-invite for editors, Publish for viewers and clients.

Two distinct flows, both launched from the Share button in the top-right of the editor:

Watch

• Share (the dialog's first tab) sends an email invite that grants edit access. The recipient can open the project, render, and save outputs as if it were their own.
• Publish (the dialog's second tab) generates a viewable, link-based version of the project. Optional commenting lets the viewer leave feedback in-context. The right tool for client review and external sign-off.

Share dialog with the Share and Publish tabs along the top, an empty email field with the Invite button, and a single People with access row

When to use which

Need	Use
External client review	Publish. Generate a link, send it. They view the rendered sequence; they don't need an Intangible account.
Asynchronous client feedback	Publish with commenting on. They drop comments on the published view; you read them in-app.
Bringing a collaborator into the actual editor	Share. They get an email invite with edit access; they open the project and work alongside you.
Handing off to another internal team	Share. Edit access lets them pick up where you left off.
Showcasing finished work in a portfolio	Publish. A polished view, no editor chrome.

How email-invite Share works

1. Click Share in the top-right of the editor.
2. Stay on the Share tab of the dialog.
3. Type the recipient's email in the field.
4. Click Invite.

The recipient gets an email with a link. They sign in (or sign up, if new); the project opens in their workspace under "Shared with me" or equivalent. They have edit access from there.

There's no "view-only" option on the email-invite path. For view access, use Publish.

How Publish works

Click Share, switch to the Publish tab, set a title, pick what to include, optionally toggle comments, click Publish, and send the resulting link. The recipient doesn't need an Intangible account. The full flow – content selection, alternate takes, the viewer experience – lives in Publish.

Render-credit billing applies only on the email-invite path. A Share-invited collaborator's renders count against their own workspace's credit balance, not yours. A Publish viewer doesn't render at all.

Sharing with someone who doesn't have an Intangible account

• Email-invite path: the link triggers sign-up. The recipient signs up; the share resolves once they confirm. They land on a free-tier account by default.
• Publish path: no account required. The viewer follows the link and watches.

For external clients, Publish is usually right – no sign-up friction, no risk of accidental edits.

Removing access

• Email-invite shares: click Share again; the list of current shares appears; click the remove icon next to a recipient; confirm. The recipient loses access immediately.
• Published links: unpublish from the same Publish tab. The link goes inactive.

Limits and known issues

• Shares are per-project. Sharing one project doesn't share other projects in the same workspace.
• No "share whole team" via the email flow. To share many projects with the same person, add them to the team workspace via Create and invite instead.
• Shared projects don't transfer ownership. The original owner remains the owner; the recipient is a collaborator. To actually transfer, use Project ownership (within a team).

Related

• Publish
• Workspaces
• Create and invite
• Permissions
• Project ownership