Sharing in meryn is split into two separate layers that are easy to conflate: who on your team can see a project, and what, if anything, is visible to people outside your team. Nothing you do in one layer affects the other.
Inside your team: project access
Every project has an access scope, set by whoever created it:
| Scope | Who can see it |
|---|---|
| Team (default) | Every member of your team. |
| Restricted | Only the creator, plus any team members explicitly added to the project, plus admins (admins and the account owner always have access regardless of scope). |
If a project is restricted, add or remove individual team members from the project's access settings at any time — this only controls visibility within your team and has nothing to do with the external sharing layer below.
Outside your team: publishing a flow
The thing you publish is a flow (an Experiment), not a model, an allocator, or the Benchmark node itself. Every model, allocator, and benchmark connected to a flow inherits that flow's visibility automatically — none of them has its own separate "public" flag. Publishing is triggered from the Benchmark node once you've set a winner: click Publish, and a read-only presentation of that winner becomes reachable outside your team, two ways.
Guests
Invite specific people by email. A guest does not join your team — they only ever see the published presentation of the flow they were invited to, never your projects list, drafts, or anything else in the workspace.
Public link
Generate a shareable link — anyone who has it can view the published presentation without logging in. Revoke it at any time to cut off access immediately; generating a new one afterward produces a different link, so an old link you shared previously won't start working again.
What a viewer sees
Whether they arrived by guest invitation or public link, a viewer sees exactly the same thing: the current winner's results and its allocator recommendation, on a clean read-only page — never a draft, never a model that wasn't chosen as the winner, and never the canvas itself.
Unpublishing
Clicking Publish again toggles it off. Clearing the winner on the Benchmark node also unpublishes the flow automatically — a published view always shows the current winner, so there's nothing correct left to show once there isn't one.