> ## Documentation Index > Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt > Use this file to discover all available pages before exploring further. # Artifacts > The artifact gallery collects web pages and reports that AI SRE sessions produce with the present_files tool and publish with the publish_artifact tool (for example, /insight reports). Search, filter by scope, rename, share, download, and delete them here. **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. ## Overview *** An artifact is a file AI SRE produces in a session with the `present_files` tool and then publishes to the artifact gallery with the `publish_artifact` tool — typically a self-contained HTML report or page. For example, the operational insight report generated by typing `/insight` in a session is an artifact. A published artifact inherits its source session's scope: artifacts from a personal session belong to their creator ("Personal"); artifacts from a session bound to a team belong to that team and can be shared with other account members. Entry point: **AI SRE → Artifacts** in the left navigation, route `/ai-sre/artifacts`. The artifact gallery has no entry point for manually uploading or creating files — every artifact is produced and published by the agent using tools during a session. The console only lets you browse, search, and manage artifacts that already exist. ## List Page *** ### Search and scope filter * **Search box**: fuzzy-search published artifacts by title; the query fires automatically 300ms after you stop typing. * **Scope**: a three-way **All / Personal / Team** switch (the same two-level scope shared with other resources under Customize). Selecting "Team" expands a searchable, multi-select team picker; selecting no team means "all teams visible to me." ### Artifact cards Each card shows: * A kind icon in the preview area: a code icon when the content type or file name is HTML, otherwise a document icon; * The title (up to two lines, truncated beyond that); * An "Edited …" relative timestamp — just now / N minutes ago / N hours ago / N days ago, or a specific date beyond 30 days; * A scope badge in the bottom right: team artifacts show the team name (highlighted green); personal artifacts show the creator's name (gray). Clicking the card body opens the artifact's detail page. Hovering over a card reveals a "More actions" button in the top-right corner (always visible on touch devices). ### Creating an artifact Click **New artifact** in the upper-right corner of the page to jump to the chat page with a prefilled draft prompt: > I want to build a publishable Artifact in Flashduty AI-SRE: a self-contained web page or report published with the publish\_artifact tool. Ask me a few focused questions about the audience, content/data, interactions, and visual style, then build it and publish it. The agent first asks you about the target audience, content/data source, interactions, and visual style, then builds and publishes the artifact — there is no form to fill out directly. Separately, any file shown in a session with `present_files` also has a "Publish to artifact gallery" button next to it, letting you publish a file that session already produced directly as an artifact — a more direct path than "New artifact" when you don't need a fresh conversation. ## Card Actions *** The "More actions" menu on each card offers: | Action | Notes | | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Copy link | Copies the full URL of the artifact's detail page, which you can share with other account members | | Download | Only appears when the artifact is linked to a file (`file_id` is non-empty); downloads the original file | | Rename | Only appears when you have edit permission on the artifact; opens a dialog to change the title | | Delete | Only appears when you have edit permission on the artifact; requires confirmation. Deleting removes the artifact from the gallery, but the source session and underlying file are unaffected | ## Detail Page *** The detail page route is `/ai-sre/artifacts/:artifactId`. The top toolbar offers: * **Title**: if you have edit permission, click the title to edit it inline (no separate form) — press Enter to save, Esc to cancel; * **Creator**: shown below the title as "Artifact by \[creator]"; * **Share**: copies the link to the artifact's detail page; * **Delete**: shown only when you have edit permission; requires confirmation; * **More actions**: this menu appears only when at least one of the following is available — * **Open session**: shown when you still have access to the artifact's source session; opens that session's full conversation (messages, tool calls, artifact history); * **Download**: shown when the artifact is linked to a file. The body renders the artifact according to its actual content type (for example, an HTML report renders inline as a page). ## Permissions *** Whether an artifact is editable (rename, delete) is determined by the `can_edit` field returned by the backend. Any one of the following grants management access: | Condition | Notes | | --------------------------------- | ------------------------------------------------------------------------------------------------- | | Creator | The owner of the session the artifact was published from | | Account Owner / admin | Has management access to any artifact in the account, personal or team scope | | Team member (team artifacts only) | When an artifact belongs to a team (`team_id > 0`), other members of that team can also manage it | Artifacts you cannot edit only expose read-only actions such as "Copy link" and "Download" — the "Rename" and "Delete" buttons do not appear. This differs from the automation rule permission model: the account Owner / admins have management access to **any** artifact, including other members' personal artifacts — there is no "no exemption for personal resources" restriction here. ## Related Pages *** Learn how sessions surface files with the present\_files tool — the source of every published artifact. The operational insight report generated by `/insight` is itself an artifact, manageable from the gallery like any other. Reports produced by scheduled automation runs can also be published as artifacts, giving them a permanent home in the gallery.