Artifacts
Artifacts
Understand saved outputs, artifact apps, drafts, versions, and the live result.
Artifacts
Understand saved outputs, artifact apps, drafts, versions, and the live result.
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.
What an artifact contains
An artifact is a saved document, report, image, data file, dashboard, app, tool, or hosted MCP server. Open it from a workspace, the library, or a chat reference. The artifact page is where you inspect the result and its settings.
Choose the right workflow
| Task | Guide |
|---|---|
| Review output and earlier versions | Preview and versions |
| Rename, place, or delete an artifact | Item details and settings |
| Build and check an app draft | Deployment and validation |
| Make a reviewed version live or roll back | Publishing |
| Collaborate inside Topline | Topline access |
| Let people use the finished app or published output | App and link access |
| Manage URLs, domains, and embeds | Addresses and embeds |
| Inspect data and recurring refreshes | Data and schedules |
Drafts, versions, and live output
A draft is work in progress. A saved version identifies an exact result. The live version is the one approved for published use. A successful build or deployed draft does not make it live. Sharing controls also distinguish collaboration inside Topline from access to the published result.
Review before accepting
Before accepting or sharing an artifact, verify:
- title, owner, workspace, and intended audience;
- source conversation or coding task;
- current draft, immutable version, and live-version identity;
- data source, generated time, refresh model, and current freshness;
- validation, rendered smoke, and acceptance evidence;
- schedules and external connections;
- sharing mode and sensitive content; and
- rollback or prior live version.
Unsupported or binary files should provide safe download guidance. Raw payload views can contain sensitive data; expand them only when necessary and do not copy them into tickets or chat without redaction.