# Artifact item details and settings

Manage names, descriptions, placement, symbols, and permanent deletion.

## 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?drawer=details`. Open the saved resource from the product rather than typing this address.

## Open Item details

Open **Item details** from the artifact or its library-row menu. Its sections include **Name and description**, **Placement**, **Schedules**, **Data**, and, for the owner, **Danger zone**. The symbol action opens the artifact's symbol setting.

## Update the artifact

Review the exact artifact and current workspace before changing its name, description, placement, or symbol. Only owners, editors, and co-authors with artifact write access can change its symbol. Viewers can inspect it.

## Lock chat changes

Use **Lock chat changes** in the header to block changes from chat and coding/workforce tasks. The **Chat changes locked** badge confirms it. Manual edits and **Refresh item** remain available; this is not a read-only lock or an access restriction. **Unlock chat changes** lets chat and workforce change the item again. If saving the lock fails, check the badge before relying on it.

## Delete an artifact

Artifact-owner deletion is irreversible. The owner deletes an artifact with
**Delete…** in the danger zone of **Item details**; an app with a managed MCP
connection must first be disconnected through **Manage MCP connection**. Before
confirming, review the Data section and any attached schedules. Deleting an artifact permanently removes
the artifact, tears down its attached schedules, and drops every registered
workspace table labeled `artifact_lifetime`, including all rows in those
tables. Tables labeled `operator_managed` or with another retention policy are
not dropped by artifact deletion. If Topline cannot safely validate or remove
an artifact-lifetime table or schedule, the artifact deletion fails instead of
silently leaving the requested cleanup incomplete. Historical audit records
remain available.

## Recovery

If saving or deletion fails, preserve the error and reopen the same artifact to check its current state. Resolve the reported schedule, table, or MCP-connection dependency before retrying. Permanent deletion cannot be used as rollback.

## Related guides

- [Data and schedules](/docs/artifact-data)
- [Workspaces](/docs/workspaces)
- [Publishing and rollback](/docs/artifact-publishing)