Sharing & Visibility
Every document is private by default - you decide when to flip it to public, where the raw file for either lives, and what forking means.
Private and public
Every document in DAI Studio is one of two visibilities, set in the editor’s Document overlay under Privacy. The lock or globe icon in the top bar shows the current setting and opens it:
| Private | Public | |
|---|---|---|
| Who can view | Only you | Anyone with the link — no sign-in needed |
| Editor page | The full editor, yours alone | A read-only version with a Read only badge |
| Indexing | Not indexed — kept out of search engines | Indexable; appears on your public profile |
| Forking | Not forkable | Visitors can click Fork Me Now to copy it into their account |
The change applies immediately — click the lock or globe (or Document), choose Private (“Only you can view”) or Public (“Anyone with the link can view”), and when public the Privacy section shows the public link to copy.
Your public profile
Your username has a public page — dai.studio/your-name — listing every document you’ve made public. It’s the natural home for showcases, examples, and work-in-progress you want feedback on. Private documents never appear there. (See Accounts & Documents for username rules.)
The raw file — public documents
Every document has a raw URL that returns the live .dai XML as plain text. For a public document it needs nothing but the URL:
https://dai.studio/your-name/document/raw
This is the link to paste into an LLM or wire into an agent — the endpoint allows cross-origin fetches, so tools and models can retrieve the current file themselves instead of aging in a chat buffer. Because it follows the document, it is always the latest saved version.
The raw file — private documents
Private documents also have a raw URL, but it carries a secret token:
https://dai.studio/your-name/document/raw/<token>
Whoever has the full link can fetch the file — the token is the credential, no session needed. You control it from the editor:
- Copy for AI in the top bar, or Document → Export → Copy URL, copies the tokenised raw link (generating the token on first use). As the owner you always get the tokenised link, even for a public document — so links you hand out keep working if you later make the document private.
- Document → Privacy → Rotate raw URL invalidates the previous token immediately and copies a fresh link to your clipboard (the button confirms with Copied new URL!). Use it when a review round ends or a link leaks.
While a document is public, every raw link works, with or without a token; rotating matters once it is private. Rotating affects only the raw link — the editor page for a private document was always yours alone.
Forking
A visitor lands on your public document, likes it, and clicks Fork Me Now: DAI Studio copies the entire file into their account as a new document. The fork:
- is theirs — they edit it independently, and your original never changes;
- starts private in their account, with a fresh URL, and counts toward their document total;
- works for anyone viewing a public document — visitors who aren’t signed in are asked to sign in first, and the fork then completes automatically.
Forking is also the easiest way to build on the community examples — open one, fork it, bend it to your domain.
Choosing how to share
| You want | Do this |
|---|---|
| Feedback or showcase | Make the document Public; share the page URL or your profile |
| A specific person or agent to read a draft | Keep it Private; share the tokenised raw URL from Copy for AI |
| A model to always read the latest version | Share the raw URL (public /raw, or private with token) instead of pasting |
| A starting point others can remix | Make it Public and let them Fork Me Now |
| Review round over, link compromised | Rotate raw URL — old links die instantly |
Two things break every link to a document at once: renaming (the document name is the last URL segment — see Accounts & Documents) and deleting. If a shared document outlives its name, send the new URL.