Chat Artifacts
đ§Ș Chat Artifacts is currently in private beta. Some workspaces and roles may not see artifact features yet. If you would like access, reach out to [email protected].
Chat artifacts turn certain generated files and app outputs from Secure Chat into reusable previews that you can inspect, edit, share, and publish.
When an artifact is available, Secure Chat shows an artifact card in the conversation. Select Preview to open the artifact viewer.
Artifact Viewer
The viewer can include:
A Preview tab for the rendered output.
A Code tab for generated source when the artifact is an app, code, or text artifact. PDF, DOCX, and PPTX document artifacts do not have a Code tab.
A Download action for document artifacts.
Version and status details, such as draft or published state.
Publish controls when your workspace and role allow publishing.
Version History
For artifacts with multiple versions, select History in the artifact viewer to view past versions and their status, such as draft, published, current, or latest.
To reuse an older version, select Restore as new draft. Restoring does not replace or delete existing versions. Hatz copies the selected version into a new draft that you can review, edit, and publish when ready.
Editing an Artifact
While an artifact is open, it stays attached to your chat. To change it, type a follow-up message in the same conversation describing what you wantâfor example, "Update the heading and add a summary section"âand Hatz revises the artifact. Each revision is saved as a new version, so your earlier versions stay available in History.
For PDF, DOCX, and PPTX artifacts, use the same side-by-side chat flow: open the document artifact, select Edit when available, and describe the change. Hatz appends the result as a new version of the same artifact instead of creating an unrelated generated file. DOCX and PDF artifacts can be reviewed in the document preview. PPTX artifacts can be edited and versioned, but currently use the download panel instead of an inline slide preview.
Publishing options
Artifacts can be published with different visibility levels:
Private: Available only to signed-in users who already have access to the chat context.
Organization: Available to members of the current workspace.
Public link: Available to anyone who has the link, including people who are not signed into Hatz. This option appears only when external artifact publishing is enabled for the organization and your role.
Choose the narrowest visibility that fits the use case. Before creating a public link, remove client data, private instructions, credentials, and other sensitive information. Anyone who receives the link can forward it.
Create and copy a public link
Open the artifact version you want to publish.
Select Publish, or Share for an artifact that is already published.
Choose Public link.
Review the artifact, then save or publish.
Select Copy public link and store the link somewhere appropriate before closing the dialog.
Open a signed-out or private browser window and test the copied link before distributing it.
Copy the link immediately. For security, Hatz shows a newly issued public URL only once. After the dialog closes, Hatz can confirm that an active link exists but cannot display that same URL again.
Publishing another version with Public link issues a new URL and stops the previous URL from working.
Manage an existing public link
Open Share on the artifact to review its public-link status.
Copy public link: Available immediately after Hatz issues a new URL and until you close the dialog.
Rotate public link: Stops the current link and issues a new one. Copy the replacement before closing the dialog.
Revoke public link: Stops the link immediately and changes the artifact to Private. People using the revoked URL receive a not-found page.
If Hatz reports that the link changed in another session, refresh the artifact before rotating, revoking, or publishing again.
What public visitors can access
A public link opens a signed-out artifact viewer. It does not give the visitor access to the source chat, your Hatz workspace, other artifact versions, or your account. Public visitors see only the version associated with the active link and the files needed to render that version.
A public link stops working when it is rotated or revoked, the artifact is deleted, external publishing is disabled, or the artifact feature is unavailable. These cases use the same not-found page so private artifact details are not disclosed.
Sharing with groups
When you publish an artifact to your Organization, the publish dialog also lets you share it with specific groups. Group sharing is additive: it grants the selected groups access, but it does not restrict who else can open the artifactâeveryone in your workspace can still open an Organization-published artifact whether or not you select groups. Group sharing is not available for Private artifacts. You need permission to share with groups, and the groups must already exist.
If Public link is unavailable
External artifact publishing is off by default and can be restricted by the MSP, organization, or role. A restrictive setting at any level prevents the Public link option from appearing.
Ask an administrator to confirm that artifact authoring and external artifact publishing are enabled for the organization and your role.
Confirm that you own the artifact and are viewing a version you are allowed to publish.
Refresh the artifact after an administrator changes the policy.
If the option remains missing even though the effective settings allow it, contact Hatz Support with the organization, artifact type, approximate time, and a screenshot of the visibility options. Do not include the public URL or artifact contents.
The example below shows the dialog when Public link is unavailable:
See Custom Roles for role-level settings.
Supported Outputs
Artifact support includes generated HTML apps, static React apps, code or text files, and supported document artifacts such as PDF, DOCX, and PPTX. Hatz can also use first-party templates when generating common outputs such as 16:9 slide decks, planning documents, project trackers, reports, and styled DOCX files. Template availability and the exact result depend on the selected model, request, and workspace rollout.
Normal markdown answers and ordinary code blocks are not automatically artifacts. Spreadsheet files and other unsupported binary outputs remain generated files rather than editable artifacts.
If you expected an artifact but do not see a preview card, Chat Artifacts may not be enabled for your workspace yet (the feature is in private betaâreach out to [email protected] for access), or the assistant may have returned a normal file or code block instead of an artifact-compatible output.