> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Artifacts

> The shippable output from your work in GetWhys. Save, edit, share, and revisit.

Buyer truth in, shippable assets out. Artifacts are where the output side of that promise lives. Anything you produce inside GetWhys that you decide to save — a drafted piece of content, a generated persona, a competitive teardown — becomes an Artifact you can edit, share, and revisit.

<AccordionGroup>
  <Accordion title="When something becomes an Artifact">
    Some outputs save automatically, others save when you ask:

    * **Generated content** inside Chat can be saved as an Artifact from the message menu
    * **Persona drafts**, **Messaging Framework drafts**, and other structured outputs save as drafts you can promote to published artifacts when ready
  </Accordion>

  <Accordion title="Where Artifacts live">
    Open **Artifacts** in the left navigation to see every Artifact across your organization (filtered by your permissions). Project Artifacts also appear inside the Project they belong to. See [Projects](/features/projects).
  </Accordion>

  <Accordion title="Editing">
    Open any Artifact to edit. Changes save automatically. Version history is preserved.
  </Accordion>

  <Accordion title="Sharing">
    Click the share button at the top of an Artifact to generate a link. Links can be:

    * **Organization-restricted** — only people in your organization can open it
    * **Public** — anyone with the link can open it

    Citations come along with the share, so anyone you send it to can see the underlying sources. See [Sharing](/account/sharing).
  </Accordion>

  <Accordion title="Deleting">
    Open the Artifact menu and choose Delete. Deleted Artifacts are permanently removed.
  </Accordion>
</AccordionGroup>

<Tip>
  Treat Artifacts as living documents, not one-off outputs. Edit the Artifact after you save it: add your own notes, prune what's irrelevant, tighten the structure. The cleaned-up version becomes the canonical reference for your team — and it's already source-linked.
</Tip>