Sharing

Share a project as a public read-only link when you want someone to read its Specification — a stakeholder reviewing a business rule, a teammate without a Leapter account, or a customer you want to walk through a calculation. Recipients see the same Specification view you do, with all the descriptions and diagrams, but cannot edit anything. This is a separate path from the deployment integrations. Sharing exposes the project for review, not for execution from another system. To call your Blueprint from an application, use the REST API or MCP.

​

Open the share dialog

There are two ways to open the share dialog:

• From inside a project, click Share in the top toolbar and choose Link.
• From the Projects page, click the ⋮ menu on a project card and choose Link.

The dialog has two states, modeled after Google Drive:

• Restricted (default) — only project members can open the project. There is no public link.
• Anyone with the link — anyone who has the URL can open the project in read-only mode.

​

Make a project public

1. Open the share dialog.
2. Toggle from Restricted to Anyone with the link.
3. Copy the generated URL.
4. Send the URL to the people you want to share with.

The URL has the form https://lab.leapter.com/p/<id>. It opens the project’s Specification view directly — no sign-in step. A globe icon appears next to the project name on the Projects page so you can tell at a glance which projects have an active public link.

​

What recipients see

Visitors with the link see exactly what you see in the Specification view:

• Type Definitions, Inputs and Outputs, every Blueprint, and the Dependencies graph
• Each Blueprint’s interactive diagram, embedded inline
• The full Contents sidebar for navigation
• The ability to run the Blueprint with their own input values, just like in Live mode

What they cannot do:

• Edit any node, description, or heading
• Trigger AI editing or the Lab Agent — the toolbar buttons that mutate the project are inert
• Add comments
• Open the deployment menu (Connect, n8n, Code, Embed are hidden)

If they have a Leapter account but no membership in the project, the same read-only experience applies; if they’re listed as a member, full edit access returns.

​

Stop sharing

Open the share dialog again and toggle back to Restricted. The public URL stops working immediately — anyone using it will get a 404. The same URL is reused if you re-enable the share later.

​

Who can share

Only project owners and team admins can manage shares:

• For a personal project, the project owner.
• For a team project, members with the owner or admin role on the team — see Teams.

Other team members and anonymous visitors don’t see the Link option.

​

Tips

• Reconcile before sharing. Ask the Lab Agent to bring the descriptions in line with the logic, so the spec readers will see actually matches what you ship. See Logic & Descriptions.
• Use one share per audience. If you need to share with multiple groups separately, that’s not yet supported — today’s share is one public URL per project. If you need fine-grained control, keep the project restricted and add reviewers as team members.
• Don’t put secrets in input examples. The shared view shows your project’s structure and any default input values. Strip anything sensitive before turning the share on.

​

What to do next

• Specification view — the experience your share recipients see
• Logic & Descriptions — keep your spec readable before you share
• Deploy & Integrate — for runtime integrations rather than review-only sharing