> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/learn-more/reference/sharing-and-collaboration.md).

# Sharing and collaboration

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

Bring a collaborator into the editor, send a client a link they can view and comment on without an account, or hand over the project's assets. All three start from the **Share** button in the top-right of the editor, which opens a popover with one tab for each: **Team**, **Publish** and **Assets**.

## Watch

{% embed url="<https://www.youtube.com/watch?v=GnBAbs3TmiM>" %}

* **Team** (the 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 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.
* **Assets** (the third tab) is for handing over the project's assets. To hand over chosen files as one ZIP, see [Asset packs](https://help.intangible.ai/canvas/asset-packs.md).

![The Share popover on its Team tab, beside Publish and Assets: an email field with Invite, and People with access listing the owner (name, email and avatar blurred)](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-6feab0cc5352f6d0a0b81ab1753d0522bbc8aa9e%2Fshare-team-tab-01.png?alt=media)

## 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 Visualize under **Comments**, at the top right. |
| Bringing a collaborator into the actual editor | **Team.** They get an email invite with edit access; they open the project and work on it too.                                             |
| Handing off to another internal team           | **Team.** 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 invites work

1. **Click Share** in the top-right of the editor.
2. **Stay on the Team tab** of the popover.
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](https://help.intangible.ai/publish/publish-tab.md).

{% hint style="info" %}
An invited collaborator's renders count against their own workspace's credit balance, not yours. A Publish viewer doesn't render at all.
{% endhint %}

## 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 and open the **Team** tab; 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

* **No live multiplayer.** Two people can edit one project, but not together in real time. Agree who edits which assets, and avoid editing the same ones at once.
* **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](https://help.intangible.ai/teams-and-billing/create-and-invite.md) instead.
* **Shared projects don't transfer ownership.** The original owner remains the owner; the recipient is a collaborator. To actually transfer, use [Project ownership](https://help.intangible.ai/teams-and-billing/project-ownership.md) (within a team).

## Related

* [Publish](https://help.intangible.ai/publish/publish-tab.md)
* [Workspaces](https://help.intangible.ai/teams-and-billing/workspaces.md)
* [Create and invite](https://help.intangible.ai/teams-and-billing/create-and-invite.md)
* [Permissions](https://help.intangible.ai/teams-and-billing/permissions.md)
* [Project ownership](https://help.intangible.ai/teams-and-billing/project-ownership.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/learn-more/reference/sharing-and-collaboration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
