Access control
Close a prototype or one version when it isn’t ready to be viewed. Members see a “request access” page, and public links to that content stop working too.
Two levels of control
- Project-level: closes every version of the prototype at once.
- Version-level: closes just that one version; everything else stays open.
Both default to open. The dashboard shows which state each project and version is in.
Per-version toggles are disabled in the dashboard while the whole project is closed. The project switch already covers everything.
Who can change it
Only the project owner (the person who created it) or an org admin can open or close a prototype. They also need a publisher seat and permission to edit its Space. If the owner has left the org, an admin with that access can act.
Requesting access
When a member hits a closed prototype, they see a form to notify the owner by email. The request does not grant access automatically. If the email fails, the requester sees the owner’s address so they can reach out directly.
If you request access several times in a short window, you’ll be asked to wait before sending again. This keeps the owner’s inbox from being flooded. Treat the form as a convenience for reaching the owner, not a way to gain access on your own.
Known limits
- Disabling a prototype closes it for new visitors immediately. Someone already in an active session may briefly see it before it refreshes.
- Closing access also closes any public link to that version. A closed prototype or version can’t be reached through a public share even if one already exists.