# How to view and share Artifacts in Helio (/work/artifacts)



## What Is an Artifact? [#what-is-an-artifact]

**Artifacts** is a gallery of pages your AI teammates publish as they work — reports, dashboards, generated pages, or previews that are easier to revisit by link than in chat. For example, ask a research teammate to publish a competitive analysis, or a growth teammate to publish a live campaign dashboard — instead of digging back through chat history, you open the artifact and the latest version is already there.

<LivePreview component="Artifacts" />

## How an Artifact Is Created [#how-an-artifact-is-created]

Only an AI teammate publishes an artifact — there's no "New Artifact" button for a person to click. When you ask a teammate for a page, it builds a single self-contained HTML page (or writes markdown, which Helio renders to HTML) and explicitly publishes it. Nothing goes live until that publish step happens.

Ask again later and the teammate can **republish** — the same link updates in place with a new version, instead of scattering a fresh link every time a report refreshes.

## Where It's Hosted and Who Can See It [#where-its-hosted-and-who-can-see-it]

A published artifact is stored as a versioned file and served at its own link — `app.helio.im/a/…` — rendered inside a locked-down sandbox with no access to your Helio session, cookies, or data, and no ability to call out to the internet. **Any signed-in member of your org can open the link; nobody outside the org can** — there's no way yet to restrict an artifact to specific people.

On desktop, opening a card hands the link to your system browser instead of rendering inside the Helio app itself — that's deliberate, not a bug: it keeps AI-generated pages fully out of the desktop app's process.

<Callout type="info">
  An artifact isn't a place to publish something meant to stay private within the team — every org member can see it. If a page contains data that shouldn't be that widely visible, ask for an attachment or a document instead.
</Callout>

## How to View and Share an Artifact [#how-to-view-and-share-an-artifact]

<Steps>
  <Step>
    ### Step 1: Ask an AI teammate to publish an artifact [#step-1-ask-an-ai-teammate-to-publish-an-artifact]

    In a task or channel, ask the teammate for a page you will revisit, such as a report, dashboard, table, or interactive mock. If you need a downloadable file instead, ask for an attachment rather than an artifact.

    <LivePreview component="AssistantChat" />
  </Step>

  <Step>
    ### Step 2: Open Artifacts from the sidebar [#step-2-open-artifacts-from-the-sidebar]

    Open **Artifacts** in the left sidebar. The gallery shows artifact cards with title, publisher, owner, version, and last edited time.

    <LivePreview component="Artifacts" />
  </Step>

  <Step>
    ### Step 3: Search or filter [#step-3-search-or-filter]

    Use search to find a title, or filter by agent when you know which teammate published it. Empty results show an empty state rather than a blank page.

    <LivePreview component="Artifacts" />
  </Step>

  <Step>
    ### Step 4: Open or share the artifact [#step-4-open-or-share-the-artifact]

    Click a card to open it — on desktop, that's your system browser; on web, a new tab. Share the link when teammates need the same page; because republishing updates the same link, it never goes stale.

    <LivePreview component="Artifacts" />
  </Step>

  <Step>
    ### Step 5: Delete only when it should disappear [#step-5-delete-only-when-it-should-disappear]

    Hover a card you own to reveal delete. Deleting is permanent, so use it for outdated or unsafe artifacts, not for normal version updates — a republish already keeps the link current without deleting anything.

    <LivePreview component="Artifacts" />
  </Step>
</Steps>

## Who Owns an Artifact [#who-owns-an-artifact]

The **publisher** is the AI teammate that created the artifact. The **owner** is the human it was made for — set once, when the teammate first publishes. Only the publishing AI teammate can republish it; either the owner or the publishing teammate can delete it. Helio keeps up to 20 previous versions, so you can open the version history in the artifact viewer and step back to an earlier one if a republish gets something wrong.