Topline Docs

Artifacts

Artifact previews, versions, and source

Inspect the current result, compare saved versions, and identify draft and live previews.

Artifact previews, versions, and source

Inspect the current result, compare saved versions, and identify draft and live previews.

Where to find it

Open Apps & Workspaces, choose the workspace, and open the artifact. Its header and drawers contain the settings for this guide.

Address: /artifacts/:id. Open the saved resource from the product rather than typing this address.

Review a version

  1. Open the artifact from the correct workspace or chat.
  2. Check its title, owner, selected version, and current live version.
  3. Review the rendered output and any available source or version information.
  4. For an app, identify whether the preview represents a private draft, a saved version, or the live app before testing it.
  5. Record the exact version you reviewed before publishing or requesting changes.

Supported document and media types use their corresponding preview. Unsupported or binary content may require downloading. Treat raw payload views as potentially sensitive.

Switch previews and refresh

Use Live to view the published version and Draft to view unpublished changes. Live is unavailable before publication; Draft is unavailable when there are no unpublished changes. Save or discard unsaved manual edits before switching versions.

Reload fetches the selected view's saved state from the server. Refresh item, when the artifact supports it and you can edit, runs the item again to pull current data. Reloading does not run a refresh, and refreshing does not publish a draft. Check the resulting version and freshness after either action.

Request a change

Describe the expected and actual result in chat with the artifact attached or mentioned. Preserve its owning context and identify the version. A new version needs its own review; earlier validation does not automatically certify changed content.

When a preview fails

Check access, the selected version, and app readiness. A missing or failed draft preview is not proof that the live app changed. Use deployment and validation for app blockers.