Artifacts

Everything Cheqq makes for you to read, present, or hand on is an artifact: the report you asked for, the deck for Monday's pitch, the pricing sheet, a picture, a clip, a PDF it rendered. Each one lands in Artifacts in the main navigation, keeps every version of itself, and can be commented on, changed, presented, downloaded, and shared from the same place — whatever kind of thing it is.

What an artifact can be

Every kind has a thumbnail, so the gallery reads at a glance.

Every format is under Share → Export, where anyone who can open the artifact can download it.

A page is different from an App: a page is self-contained and needs nothing running behind it, while an App is a published site with its own data and domain. An interactive page remembers what you did in it — the boxes you ticked, the fields you filled — when you come back to it in the same browser.

Where artifacts come from

• From a conversation. Ask for a page, a document, a spreadsheet, or a deck — or start from Pages, Docs, Sheets, or Slides on the chat home. The same goes for the chats inside a Wapp, a workflow, or the App Builder.
• Pictures and videos. Everything Image and Video mode make, and every picture or clip Cheqq generates mid-task, is kept in Artifacts the moment it exists. An edit of an earlier picture becomes that picture's next version.
• Finished files. When Cheqq finishes a file some other way — a PDF it rendered, a CSV it exported, a chart — it can keep it as an artifact too.
• Your own files. Save any workspace file to Artifacts from Files. It's a copy: the file stays in Files, so anything that reads it from there keeps working.
• Field Agents. A picture or video a Field Agent makes is kept in the Artifacts of whoever ran it, and the record links to it. Everyone who can read the record can still open it.

A collection's file field can also link an artifact rather than hold a copy of it: the record then always shows the artifact's latest version.

An artifact and its conversation

While Cheqq is writing an artifact, it holds its place in the conversation. When it's done, a card opens it beside the chat, and a chip above the composer keeps it one click away for the rest of the thread.

An artifact also has a page of its own, which opens on the artifact alone — so you can present it without the conversation that made it on screen. From there, Open conversation takes you back to the thread where it was made, with everything that shaped it. An artifact with no conversation behind it — a file you kept, one shared with you — has a Chat button instead, which opens a conversation about that artifact beside it.

Versions

Every change is a version, whoever made it: Cheqq's rewrite, your edit, a tweak, a restore. One thing you did is one version — retyping a heading and recolouring it is a single entry, not two.

Nothing in the history is ever rewritten. Restoring an old version makes it the newest one again, so a restore can itself be undone. Restoring a chat checkpoint rewinds the artifacts the rewound turns changed, the same way.

Who can open it

An artifact is private when it's made. Only you can open it until you decide otherwise, and only its owner can change who has access.

You can also invite people one at a time, by email, as one of three roles:

• Viewer — can read it.
• Commenter — can read it and leave comments.
• Editor — can change it and restore earlier versions.

Publishing

Choosing Anyone with the link or Public on the web publishes the artifact: it gets a public page that opens without signing in. A published link shows the version it was published with, so later edits stay private until you move the link to the latest version.

A published artifact carries a small Created with Cheqq mark, depending on the plan of the workspace that owns it:

See Billing for plans. Visitors to a published artifact can make a copy of their own when you allow it — see Share and remix.

Continue with Work with artifacts.