Not every page should become a collaboration surface. Sometimes you just need to publish a spec, a brief, a checklist, or a project note so someone else can read it without changing the source.
That is the core rule behind Yoinko page sharing: shared pages are always read-only. Viewers can read the published page, but they cannot edit the original workspace content. The source remains inside your workspace, under your control.
Password protection is optional. If a page is meant for a small client handoff, a private team update, or a temporary review link, add a password before publishing. If it is meant to be public, leave the password off and share the link.
This keeps sharing separate from editing. Editing belongs in the workspace. Sharing belongs at the edge, where the goal is distribution, review, or handoff.
It also fits the rest of Yoinko's model. Pages can be locked to prevent accidental edits, folders keep content organized, and shared links expose only the read-only view you choose to publish.
The result is simple: publish the page, decide whether it needs a password, and share it without giving up control of the original.