# Artifacts

Open, use, change, and delete the live pages that the Assistant builds for you: custom dashboards and small internal tools that run your organization's tools.

An artifact is a page that the [Assistant](https://www.tryrisotto.com/docs/dashboard/assistant) builds for you: a custom dashboard, a live view of your organization's data, or a small internal tool, such as a list of stale tickets with a button to assign each one. The page gets its data, and makes its changes, by running the tools that you let it use. The **Artifacts** page in the sidebar lists every artifact in your organization.

> **Note:** Only Org Admins and Managers see **Artifacts** in the sidebar and can open an
> artifact. A department Supervisor can use the Assistant, but cannot build or
> open artifacts.

## What an artifact is

- **One page.** Each artifact has a title, a short description, and a web page that the Assistant writes. Risotto adds the dashboard's styles to the page, so it looks like the rest of the dashboard and follows your light or dark theme.
- **A tool grant.** The Assistant gives each page the tools it needs, and no others. A page can use Risotto's built-in tools, such as **List tickets** and **Update ticket**, and your organization's enabled [tools](https://www.tryrisotto.com/docs/dashboard/tools). Risotto refuses a call to any tool outside the page's grant.
- **A sandbox.** The page runs in a sandbox inside the dashboard. It cannot load anything from the internet, and it cannot reach your dashboard session. The only way it gets data or changes anything is to run one of its granted tools.

A page cannot run the tools that build or change artifacts, the tools that ask for credentials, or the tools that set up custom API sources and external MCP servers.

The files that the Assistant saves in a conversation, such as a `.csv` export, are not artifacts. They stay in the conversation where they were saved and do not appear on the **Artifacts** page. See [What it does](https://www.tryrisotto.com/docs/dashboard/assistant#what-it-does).

## Build an artifact

You build an artifact by asking the Assistant for it. You need the Org Admin or Manager role.

1. **Open a new conversation**

   On the **Artifacts** page, click **New artifact**. It opens a new
   conversation on the Assistant page. You can also start from any Assistant
   conversation.

2. **Describe the page**

   Say what the page shows and what it lets you do. For example: "Build me a
   page that lists open IT tickets with no update for three days, with a button
   to assign each one to me." The Assistant picks the tools the page needs and
   writes the page.

3. **Approve the Create Artifact card**

   In **Read only** mode, a **Tool approval** card for **Create Artifact**
   shows the page's `title`, `description`, `html` (folded), and
   `allowed_tools`, the tools the page may run. Click **Approve**.

   *Product example: A Create Artifact approval card in an Assistant conversation, with the page's title, HTML and granted tools, and Approve highlighted.*

4. **Open the page**

   The Assistant replies with a link to the new page. Click it to open the
   artifact. The artifact also appears on the **Artifacts** page.

Building or changing an artifact counts as a change, so it runs without a card in **Auto-accept changes** mode. Deleting one runs without a card only in **Auto-accept everything** mode. See [Approval mode](https://www.tryrisotto.com/docs/dashboard/assistant#approval-mode).

An artifact belongs to your organization, not to the conversation that built it. Archiving the conversation does not remove the artifact, and the Assistant can find and change an artifact from any conversation. The **Create Artifact** call stays in the conversation's tool activity, so an Org Admin can see it in [All sessions](https://www.tryrisotto.com/docs/dashboard/assistant#sessions).

## The Artifacts list

Click **Artifacts** in the sidebar. The page shows one card per artifact, with the most recently updated first.

*Product example: The Artifacts page: four artifact cards with their tools, creator and last update, the search, and New artifact.*

Each card shows:

- The artifact's title and description.
- The number of tools the page may run, or **No tools**. Point at the number to see the tools under **Granted tools**.
- The email of the person who built it.
- When it was last updated, such as "12 minutes ago". Point at it to see the date and time.

Type in **Search artifacts** to find an artifact by its title, its description, or its builder's email. The list has no other filters or sort options. If nothing matches, click **Clear search**.

With no artifacts yet, the page shows "No artifacts yet" and **Open Assistant**, which starts a new conversation.

Every Org Admin and Manager sees every artifact in the organization, whoever built it. To share an artifact with another Org Admin or Manager, send them its link.

## Open an artifact

Click an artifact's card. The page opens in the dashboard, under **Artifacts** in the breadcrumb.

*Product example: An open artifact, Stale IT tickets, with its List tickets and Update ticket badges in the header.*

The header shows a badge for each tool that the page may run:

- A badge with a pencil marks a tool that makes changes. The page asks you to confirm each time it runs one.
- A red badge marks a tool that is no longer available, because it was turned off or deleted. A call to it fails.

### Who the page runs as

A page runs its tools as **you**, the person viewing it, not as the person who built it:

- Built-in tools see only the tickets of the departments where you can read tickets, also when you are an Org Admin. If you cannot read tickets in any department, every tool call fails with "Refused: you are not a member of any departments." See [Permissions](https://www.tryrisotto.com/docs/operating/permissions).
- Your organization's tools run with the credentials configured on each tool.
- Risotto records every tool call that a page makes, with the email of the person viewing it. The record is kept when the artifact is deleted.

### Allow a tool that makes changes

When the page runs a tool that makes changes, the dashboard asks you first. The page cannot answer for you. This happens on every run, whatever your Assistant approval mode.

1. **Click the page's button**

   Click the control on the page that makes the change, such as **Assign to
   me**. The pages are built by the Assistant, so the controls differ from page
   to page.

2. **Review the parameters**

   A dialog asks **Run "\<tool>"?** and shows the parameters the page wants
   to run the tool with.

3. **Allow or deny it**

   Click **Allow** to run the tool. Click **Deny**, or close the dialog, to
   cancel the call. The page then gets an error that says you denied it.

   *Product example: The Run Update ticket? confirmation over an artifact, with the parameters and Allow highlighted.*

If the page asks for several changes at once, the dialog shows them one at a time.

## Change an artifact

The dashboard has no editor for artifacts, and no rename, download, or version history. To change an artifact's title, description, page, or tools, ask the Assistant.

1. **Ask for the change**

   In any Assistant conversation, name the artifact and say what to change. For
   example: "On Stale IT tickets, add a column for the requester."

2. **Approve the Update Artifact card**

   In **Read only** mode, click **Approve** on the **Update Artifact** card.

3. **Open the artifact again**

   Open the artifact, or reload it if it is already open, to see the new
   version.

The Assistant replaces the whole page when it changes it. Risotto does not keep the earlier version of the page.

## Delete an artifact

1. **Open the Artifacts page**

   Click **Artifacts** in the sidebar.

2. **Click the trash icon**

   Point at the artifact's card. Click the trash icon in its top-right corner.

3. **Confirm**

   The dialog asks **Delete "\<title>"?** Click **Confirm**. Risotto shows
   "Artifact deleted".

   *Product example: The Delete Stale IT tickets? confirmation over the Artifacts page, with Confirm highlighted.*

The artifact disappears from the dashboard, and its link stops working. You cannot restore it. The record of its tool calls is kept. You can also ask the Assistant to delete an artifact.

## Limits

- A page's document can be up to 512 KB. A longer title is cut to 255 characters.
- A page can run up to 60 tool calls a minute. Beyond that, a call fails with "Rate limit exceeded. Too many tool invocations." Risotto also limits each viewer to 600 artifact tool calls an hour.
- While the dashboard tab is in the background, the page's tool calls wait. When you come back to the tab, each waiting call runs once.

Through the [Risotto MCP server](https://www.tryrisotto.com/docs/integrations/mcp-server#available-tools), a client with the `artifacts:read` and `artifacts:write` scopes can also list, build, change, and delete artifacts.

Source: https://www.tryrisotto.com/docs/dashboard/artifacts
