Share a secret, questionnaire, report, calculator, project database, or handover — privately.Share a secretquestionnairereportcalculatorproject databasehandover — privately.
Publish self-contained HTML artefacts with stable private links and retained versions. Publication is private immediately; external readers get in only through a visitor share you deliberately create.
Turn reports, forms, calculators, handovers, and small tools into one complete HTML document. You read it while signed in; any external reader needs a visitor share you create on purpose.
01 · Secrets
Share a secret with an end date.
Put a credential or sensitive note behind a visitor share with its own optional password and expiry, and revoke it when the job is done.
Create one named link per recipient. Names tell links apart; links can be forwarded, so they do not prove who opened them.
02 · Questionnaires
Collect answers with native forms.
Readers submit responses through native HTML forms into a project collection: signed-out visitors too, through a visitor share, when the collection allows visitors.
File fields take private, resumable uploads that stay sealed at rest and reachable only through their record. This is not public file hosting.
03 · Project database
Keep shared records next to the documents.
Artefacts in one top-level folder share declarative project collections. Editors and agents maintain the records through the in-viewer SDK, the API, or MCP.
Structured records, not SQL or realtime sync.
04 · Reports & handovers
Hand over one link that stays put.
An artefact keeps its private link through updates and moves. Retained versions let you inspect or download an earlier one, or restore it as a new live version.
05 · Tools & calculators
Ship a working tool, not a screenshot.
Inline JavaScript, CSS, and SVG run in an isolated sandbox with no external network access at view time.
Through window.artefacts.storage a tool saves encrypted JSON: personal data per reader, shared data per artefact.
06 · Made by AI
Let your agent publish it.
Agents publish or update synchronously and privately through the write API or MCP. Give yours the copyable AI briefing, also available as llms.txt. Sharing stays your explicit decision in the console.
Motion guide · six scenes
From invitation to a living artefact
A short, hands-on tour of the real Artefacts67 workflow: join securely, publish one self-contained HTML document, organize it, share it with the right boundary, and keep its source and application data understandable.
Illustrative demo. These miniature screens use placeholder content only. Nothing here uploads, sends email, creates a key, publishes a document, or writes application data.
Scene 1 of 6: Join securelyUse the scene buttons or seek bar · no audio
01 · Account boundary
Accept an invitation, then prove who you are
Accounts are invitation-only. The invite is single-use and time-limited; sign-in then asks for the account password and a current six-digit authenticator code, with an enrolled passkey as an alternative second factor.
Open the invitation and activate the account.
Sign in with the invited email and account password.
Complete TOTP or the enrolled passkey check.
Arrive at your own estate; membership is not resource access.
Passwords and authenticator codes are never part of a document link.
secure workspaceillustrative
Join the teamInvitation acceptedPassword checkedSecond factor
Sign in
Only invited users can enter.
invited colleagueemail
••••••••••password
Authenticator codeTOTP
✓ Workspace ready
02 · Publish once
Bring one complete HTML document
New artefact starts in the console. Pick an editable folder, give the document a title and lowercase path, then paste a complete UTF-8 HTML file with inline CSS, JavaScript, SVG, and embedded images into the HTML document field.
Choose or create a destination folder.
Set title, path, and language.
The server validates the self-contained document during publication.
Publication is live and private immediately; API callers see 201 for create or 200 for update.
No publish job needs polling. Ordinary links require authorized sign-in, with or without a password. Review warnings.
self-contained source
index.html
New artefact
Example project
project-handover
Complete document pasted
Inline assets and structure checked
Live now · no polling required
03 · Find and read
Folders, a focused viewer, and a useful toolbar
Your estate sidebar keeps folders, subfolders, unfiled artefacts, and Shared with you in view. Select a document to preview it beside the tree, then use Preview / Code and the title menu without losing the running document.
Open the folder tree and select an artefact.
Preview the isolated document in the reader.
Switch Preview / Code or copy permitted HTML.
Refresh, download, fullscreen, report, or manage by authority.
Preview / Code, Share, Download, and Fullscreen stay visible on narrow viewers. Console preview bypasses the additional document-password prompt, never resource authority.
Project handover
PreviewCode⋯
isolated viewer
04 · Share deliberately
A visitor link is not a colleague grant
Ordinary URLs and aliases are private: a current signed-in session with completed second factor and read authority is required. Managers and owners must explicitly create an active named visitor share for external readers. Colleague access is a separate folder grant to an invited active user.
Choose the scope, name, expiry, and optional share password.
Copy or explicitly request delivery; a password is never emailed.
Grant a colleague a role on the folder when account access is intended.
Recheck inherited access before moving or changing a resource.
A document password alone never grants access; removing it or duplicating without one never makes content public. Visitor shares have independent passwords and never grant shared-data writes.
Visitor share
A named bearer link for an external reader; optional password and expiry.
scope: handoverexpires: 30 daysreadshared write: noOrdinary gate unchangedForwarding the link still forwards its access.
≠
Colleague grant
An invited active user receives standing access to a folder and its descendants.
role: Viewerrole: Editorrole: ManagerOwner controls grantsCurrent grants are checked again on use.
Same folder · different authority boundary
05 · Keep history legible
Update the source without moving the link
Publishing replacement HTML creates the next version at the same artefact path. Retained versions can be inspected or downloaded; restoring one appends a new live version instead of rewinding history.
Publish replacement HTML from Content & versions.
See the stable path point at the new live version.
Inspect or download retained source history.
Restore as a new version when an older source is the right starting point.
Source restoration does not roll application data back.
Version history
v2Live nowtoday
v1Retainedyesterday
v0Retaineddraft
Restore as v3
Current source · v2
<title>Project handover</title><main>…</main>
example-project/project-handover
06 · Store inside the viewer
Personal and shared data have different doors
A published application can use window.artefacts.storage for encrypted JSON. Personal data is the default per reader; { scope: "shared" } is readable by authorized readers but writable only by current Editors, Managers, or Owners.
Read and set a personal preference through the SDK.
List keys with a prefix; handle rejected promises.
Use the shared scope only when the current role can write it.
Source updates preserve data; a downloaded file has no hosted SDK.
A visitor share can read shared values, but it never grants shared-write authority.
Standalone downloadNo hosted viewer, no SDK persistence.
Examples
The report template example is a complete report design with neutral sample content; agents on our instance use it as the fallback design template when you specify no design of your own.