Share, present and print
Who can see an artifact, public share links you can revoke, present mode with notes, printing to PDF, PowerPoint downloads, and why a free-form HTML page runs sandboxed.
Inside the organisation
An artifact is private until its owner sets its visibility to a team or the whole org, and shared_level to view or edit
(the rules). Nobody can open an artifact they may not see by guessing its id: it
answers "No such artifact", the same as a missing one, and another organisation's ids reach nothing.
Public links
studio_share_create (or the Share button) makes a public link, /s/<token>. Anyone with it can view the artifact without signing in.
- The token is random and long enough that it cannot be guessed. Only its hash is used to look it up.
- A link can expire (
expires_in_days) and can show the speaker notes (include_notes); by default it does not. - An artifact has at most five.
studio_share_listshows them (the owner and org admins see them) andstudio_share_revokeends one, or all, at once. - Deleting the artifact ends its links, and restoring it does not bring them back.
- A public page shows the artifact and nothing else of your organisation: no other artifacts, no names, no links back into the console.
- Links are never indexed by search engines.
Present
A deck opens full screen at /studio/<id>/present (or /s/<token>/present). Arrow keys, space, Page Up and Page Down move; Home and
End jump; O (or G) opens an overview of every slide, where a click or Enter opens one and Escape closes it; N shows the
speaker notes; F toggles full screen; swipe on a touch screen. The corner shows the slide number and the count ("3 / 12"), and the
slide number is in the address, so a link can open at slide 4. Without scripts the page shows every slide in order. Notes are never
printed from present mode.
Print and PDF
Print / Save as PDF on the artifact's page (and on a public link's page) opens the print view, /studio/<id>/print or
/s/<token>/print. Its bar has the button that opens the browser's print dialog, where "Save as PDF" makes the PDF; the bar itself
never prints. Studio does not render PDFs on the server: the browser does it, so charts stay vector and text stays selectable.
| Artifact | What prints | Options |
|---|---|---|
| deck | one slide per sheet, backgrounds kept, nothing of the app around it | the paper: 16:9 (the default, the slide fills the sheet), A4 or Letter landscape (the slide centred); Notes pages: portrait sheets with each slide and its speaker notes under it |
| page | the page on A4 (default) or Letter with 16 mm margins; a block is not split across sheets, except tables, which break between rows and repeat their header | A4, Letter |
| html | the page itself, as the browser prints it; a deck built from vk-slide sections prints one slide per sheet |
16:9, A4, Letter for a slide deck; A4, Letter otherwise |
The options are in the address too: ?size=a4 or ?size=letter, ?notes=1 for notes pages (on a public link, only if the link was
made with notes), and ?auto=1 to open the print dialog when the page has loaded. Ctrl+P (⌘P) on the artifact's page opens the
print view instead of printing the console.
An html artifact normally runs in a sandboxed frame inside a wrapper page, and printing that wrapper would print a frame. Its print
view is the page itself at the top level, served with the frame's own headers: the same Content-Security-Policy (no network, no
forms, no frames) and sandbox as a header, so it is still an opaque origin with no access to cookies or storage. The one addition
is allow-modals, because the browser's print dialog is a modal; the print view adds the bar and its print CSS to the page.
Agents get the same thing with studio_artifact_export format print (page_size, notes): the print view's address and the
print-ready document.
PowerPoint
/studio/<id>/pptx (or /s/<token>/pptx) downloads a deck as a PowerPoint file (.pptx, 16:9). It opens in PowerPoint, Keynote,
Google Slides and LibreOffice, and almost everything in it stays editable:
- Titles, subtitles, text, bullets, quotes, KPI tiles and the big number are text boxes in the theme's colours. The theme's heading and body fonts are the file's theme fonts, so changing them in PowerPoint restyles the deck. A web font stack becomes the closest font every office suite has: Arial for sans and rounded, Georgia for serif, Courier New for mono.
- Tables are PowerPoint tables. A table too long for the slide is shrunk a little, then cut, with a line saying how many rows are left out.
- Charts and diagrams are drawn as grouped shapes and text, from the same geometry as the web, so they look the same everywhere and you can recolour them or change a label. They are not PowerPoint chart objects: there is no datasheet to edit behind them.
- Speaker notes are the notes of each slide, and the slide number is a slide number field. Title, section and closing slides keep their accent background and rule.
- An image given as a
data:URI (PNG, JPEG or GIF) is embedded. An image from anhttpsaddress is not downloaded when the file is made (the server never fetches it): the slide gets a box with its alt text and a link to the image. WebP data images get the same box.
?scheme=dark or ?scheme=light picks the palette of a theme that has both. On a public link the file has speaker notes only if
the link was made with them. Only a deck exports this way: a page prints to PDF or exports as markdown or html, and an HTML
artifact exports as its own HTML. Agents get the same file from studio_artifact_export with format: "pptx": the download address,
and the file as base64 when it fits in max_chars.
HTML pages are sandboxed
A free-form HTML artifact is untrusted: whoever wrote it controls every byte, and a public link shows it to people outside your
organisation. So Studio never puts it in a console page. It serves the page from its own address (/studio/<id>/frame) with these
rules, and embeds it only in an iframe whose sandbox is allow-scripts and nothing else:
- no
allow-same-origin: the page runs in an opaque origin and cannot read the console's cookies, storage or pages; - a Content-Security-Policy of
default-src 'none'that also allows no network (connect-src 'none'), no forms, no frames, no<base>, and images and fonts only asdata:URIs, so an HTML page cannot load or send anything, and a viewer's address is not disclosed to a third party; - scripts may run, inline only, so a chart or a small interaction works;
nosniff, no referrer, and no caching.
Studio warns when a page asks for something the sandbox will block (a script src, an external stylesheet or image, a form, a
fetch). The page is edited by anchored string edits, like any text.