Sharing and embedding.

Choose the kind of access your recipient needs before creating a link.

Intended use	Share
Inspect or reuse project work	A project share using its offered options
Start a new workflow from a reusable graph	A supported template link
Run chosen inputs and receive results	A Station link
Collaborate on team-owned resources	Team membership with the right role

#Choose access for the recipient’s job

A project share or embed allows read-only inspection. Allow cloning lets an eligible visitor save an independent copy. Team membership and its role govern collaboration on team-owned resources. A Station provides controlled inputs and results under its own access rules. Revoking a share ends future link access but cannot recall files or copies already retained by a recipient.

The recipient map branches to a read-only view, role-governed team work or a Station input/result interface. Revoking the illustrated inspection link leaves an already-retained independent clone B intact.

#Share a project

Open the project's sharing controls, review the offered settings, and create the link. Check its expiry and what it includes. Share the resulting URL with the intended recipient, and use Shared Links to inspect or revoke existing shares when needed.

A share link can reveal graph structure, outputs, and supporting material according to its options. Review the project before distributing it. A shared link is not permission to publish someone else's private input data elsewhere.

#Embed a view

Use the project's embed controls to obtain the generated embed code. Keep the link and supported options from that dialog rather than constructing an internal application URL yourself. Test the embed as a recipient, including on a small screen and in a browser that is not signed into your author account.

An embed presents the supported shared view. A Station is the dedicated surface for letting people run a controlled workflow with their own account.

#Change access later

Revoke a project share when that link should stop granting access. Use a Station's Access controls or Take down Station for its runnable link. Removing a gallery listing affects discovery and does not by itself take down the Station.

Recipients can already have downloaded copies. Revoking a link does not recall those files, so choose the initial audience and bundled data accordingly.

#Separate viewing, copying, collaboration, and running

View: a project share/embed presents read-only graph inspection. Copy: Allow cloning permits an eligible visitor to save a separate project, not edit the source. Run: a Station provides controlled inputs and results under its access rules. Team collaboration is a separate membership/role grant. Revocation prevents future link access but does not recall files or copies already retained. No share or permission is created here.

#Checks and next steps

The project Share & Embed dialog offers Create Share, expiry, and Allow cloning, followed by Share URL and Embed Code. The public graph view is read-only. If cloning is allowed and the recipient is eligible, they can save a separate copy; they do not gain edit access to your source project through that option.

Use team membership and the appropriate role for collaboration on team-owned work. Use a Station when a visitor should supply controlled inputs and run a published workflow. Neither a public view nor a copy permission is the same as team editing authority.

Supported web-app outputs can also have shared links; inspect that share's own content and options. Shared Links manages distinct share categories and inactive or expired entries. Test the actual recipient experience after creating or changing a link, including what data was bundled and whether cloning is offered.