Every project you save is private by default. Flipping one to public lets anyone open it and remix it — without risking your original.
Making a project public
Click the file-name pill in the menu bar.
Flip the Public / Private toggle.
Confirm the change in the modal. Public and private can be flipped either direction at any time.
Only the owner of a project can flip its visibility. The toggle in the pill grays out when you’re viewing someone else’s public project.
Who sees what
Private projects appear only in your own Private tab under File → Load. Every project still has a /p/<slug>editor URL; visitors who aren’t signed in as you (or invited as a collaborator) see a login gate instead of the graph.
Public projectsappear in the Public tab for everyone, including visitors who aren’t signed in. Authorship is displayed next to the title. The same slug also unlocks a /live/<slug> client view.
Your own public projects also show up in your Private tab (so you never lose track of them).
Ownership rules
Ownership is enforced by row-level security in the database, so the rules below are literally guaranteed — not just UI conventions:
The user who first saved the project is the permanent owner.
Only the owner can rename, overwrite, or delete the project.
Only the owner can change visibility.
Anyone who’s signed in (plus anonymous visitors, once search is wired up) can view a public project.
Saving a copy of someone else’s project
If you open a public project authored by someone else and start editing, the menu-bar pill dims its rename field and visibility toggle — you can’t mutate the original. Hitting Save in this state does something different: it forks a private copy into your own account.
The new copy’s name is the original with _copy appended.
The copy starts private, regardless of the original’s visibility.
From that point on you own the copy, and all the normal rename / overwrite / visibility controls apply.
A saved a copy toast confirms what happened.
This means it’s impossible to accidentally stomp on someone else’s public work, even if you forget you opened their project. Save always preserves the original.
Authorship display
Public project tiles show “by <display name>” under the title. The display name comes from your OAuth profile — whatever Google passed through at signup, stored in a public profiles table.
Projects you authored show as “by you” in the Public tab, so you can spot your own public work mixed in with the feed.
Named live links
A public project’s live link is normally /live/<random slug>. You can opt into a readable alias built from your handle and the project title:
toolbox.design/@hallan/orbit
Open File → Project Settings… (or the gear chip in a Parameters panel) and switch on Use the project title in the live link. The address is previewed; hit Save to claim it. The project has to be public and saved to the cloud first.
The slug is frozen when you save. Renaming the project later never moves a link you’ve already shared — the settings row offers an Update link action when the title has drifted, and you decide.
Two of your projects can’t share an address. Saving a slug another of your projects already uses fails with a message; rename one of them first. Other users’ projects never collide with yours, because the URL carries your handle.
The random /live/<slug> link keeps working, so switching the named link off (or flipping the project private and back) never breaks it.
Your handle is the @name half. One is assigned from your email at signup; change it from the account menu (top-right) → handle → Change. Handles are 3–32 lowercase letters, digits and dashes, unique across Toolbox. Changing your handle changes every named link you own — the random links are unaffected.