Sharing a design
Publish a design as an encrypted read-only link that plays as a prototype in any browser, optionally password protected, with pinned comments you can revoke at any time.
A design is worth more in front of someone else. Studio publishes one as a read-only link that opens in any browser, with no Pathrule account on the other end.
What gets published, and what we can see
The share payload is encrypted on your machine before upload, and the key travels in the link's # fragment. Browsers never send a fragment to a server, so the viewer decrypts client-side and Pathrule holds ciphertext it cannot read. That is the whole point of the design: a public link should not mean a readable copy on someone else's disk.
Two consequences worth stating plainly:
- Anyone who has the link can open it. Encryption protects the content from us and from anyone without the link, not from someone the link was forwarded to. Add a password to the link when the audience should be narrower.
- Revoking works forward, not backward. Revoking stops the viewer serving the design. It cannot retract a copy already opened by someone who had the link.
It plays, it does not just render
The share carries the flow graph, so the viewer runs the prototype: transitions, walk back, overlays, hover states, and timeouts, inside the device the design was published for. If no device was chosen, each screen plays at its authored canvas size.
The viewer is strictly read-only. There is no connect tool and no write path back into your workspace.
Comments
A shared link can carry pinned comments. Someone with the link drops a pin on the spot they mean, and the comment appears live on your side, attached to a place instead of a paragraph of description. Comments can be turned off for a link at any time.
The team library
On a Team plan, designs your teammates author appear in a members-only library inside your organization. You can watch them update live and comment on them without anyone publishing a public link at all. Use the team library for work in progress, and a share link for the people outside it.
What to read next
- Flows and prototypes for what the viewer is playing.
- Real-time collaboration for how team surfaces stay in sync.