> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryflowy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Sharing Projects

> Invite collaborators, approve access requests, and publish a view-only share link.

export const DemoVideo = ({src, poster, caption, aspectRatio = "16 / 10", className = ""}) => {
  return <figure className={`not-prose my-6 w-full ${className}`}>
      <div className="overflow-hidden rounded-2xl border border-gray-950/10 bg-gray-100 dark:border-white/10 dark:bg-white/5" style={{
    aspectRatio
  }}>
        <video src={src} poster={poster} loop autoPlay muted playsInline className="h-full w-full object-cover" />
      </div>
      {caption && <figcaption className="mt-2 text-center text-sm text-gray-500 dark:text-gray-400">
          {caption}
        </figcaption>}
    </figure>;
};

Share a project to bring people onto the same live canvas, or hand out a public link that shows the project's media to anyone. Both live in the **Share** dialog, opened from the Share button in the editor header.

<DemoVideo src="/videos/collab/sharing.mp4" poster="/images/posters/collab/sharing.jpg" caption="Inviting a collaborator by email and turning on a public share link" />

## Invite people to a project

In the Share dialog, type one or more email addresses — each valid address becomes a chip — pick whether they can **edit** or **view**, then send. Invitees are notified and the project appears in their workspace once they accept.

Two limits shape invites:

* **Role ceiling** — anyone with access can invite, but only at roles up to their own. Editors can share as Editor or Viewer; Viewers can only share view access. See [Roles & permissions](/collaboration/roles).
* **Collaborator cap** — a project supports up to 5 direct collaborators, on top of the access workspace members already have.

## Manage who has access

The Share dialog lists everyone with access: the owner, direct collaborators, and pending invites. Owners can change a collaborator's role from the badge on their row, or remove them — removal takes effect immediately.

When a workspace role gives someone more access than their project share, the list says so — for example "Viewer · inherits Editor from workspace" — so you always see the access that actually applies.

## Access requests

Someone with view-only access can ask to edit right from the canvas: Viewers see a banner with a **Request access** button.

<Steps>
  <Step title="Spot the request">
    New requests show as a dot on the project's Share button, and appear as rows at the top of the Share dialog — "Ana wants to edit", with the requester's email.
  </Step>

  <Step title="Review who's asking">
    Check the name and email so you grant access to the right person.
  </Step>

  <Step title="Accept or decline">
    **Accept** grants the requested access on the spot; **Decline** leaves them as they are.
  </Step>
</Steps>

## Share links

At the bottom of the Share dialog, the link-access control decides who a copied link works for:

* **Only people with access** (default) — the project link only opens for invited people and workspace members.
* **Anyone with the link** — creates a public share link. Anyone who opens it sees a read-only gallery of the project's title and generated media — images, video, and audio. They can't open the canvas, edit anything, or see your nodes.

**Copy link** copies whichever link is active. Switching to "Anyone with the link" also copies the new public link for you. Only the project owner can change link access.

## Revoke a share link

Switch the link-access control back to **Only people with access**. The public link stops working immediately — anyone who visits it afterwards sees that the link is no longer available.

<Tip>
  Not sure which role to hand out? Start people as Viewers — they can always request edit access, and you can approve it in one click.
</Tip>