# Use artifacts and office documents

Artifacts keep useful outputs available beyond the message that produced them. Use the library to find, group, inspect, and iterate on those outputs.

## Find and organize an artifact
Open **Artifacts**, search for the output, and open its detail view. Group it into a collection where useful. Check the content and the referenced files before sharing it. A preview is not proof that every linked asset is self-contained.

## Iterate on the result
Use the artifact iteration surface to request a specific revision. Name what should change and what should stay. Review the new output and version before adopting it.

## Generated office files
Word, Excel, and PowerPoint outputs can be downloaded. **Settings → Documents** controls whether supported editing is enabled. The structural Word editor recreates a document from the structure it can parse; unsupported comments, footnotes, embedded objects, and exact styling may not survive a save.

Read the unsupported-content notice before the first edit and again in the save confirmation. The starting version remains available through **Details → Versions**. Keep editing disabled when preserving the original structure matters more than changing it in Gideon.

## Use artifacts elsewhere
You can save a file as an artifact, index artifacts for Knowledge search, or pin an eligible saved artifact as a dashboard tile. Each has separate setup. See [widgets and Home](/docs/capabilities/widgets-and-home).

## Review before delivery
Open the final file and check links, layout, source claims, and export behavior. Treat a warning about a missing copied file as a real dependency on the original workspace.