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

# List Reports

> Browse, search, and filter the reports inside a client's workspace.

Every report lives inside a client. Open a client to reach its **Reports** tab, which lists every report and dashboard for that client. Use it to find, open, or manage any report.

## Filter and search

* **Search** — type in the search bar to match by report name.
* **Type filter** — show only **Multi-Page Reports** or only **Dashboards**.
* **Sort** — switch between recent activity, name, type, and date created.

## What's in the list

| Column            | Description                                |
| ----------------- | ------------------------------------------ |
| **Name**          | Click the name to open the report.         |
| **Date Created**  | When the report was created.               |
| **Last Modified** | Timestamp of the most recent save.         |
| **Type**          | Multi-Page Report or Dashboard badge.      |
| **Automations**   | Count of active automations on the report. |

<Tip>
  Use consistent report naming — including month and year (e.g. *Paid Social — March 2026*) — to make the list searchable as it grows.
</Tip>

## Quick actions

From any row's three-dot menu:

* **View** — open the report.
* **Edit** — open it in the editor.
* **Duplicate** — see [Duplicate Report](/reports/duplicate).
* **Save As Template** — see [Add Template](/templates/add).
* **View Automations** — jump to the automations for this report.
* **Archive** — moves the report to the [Archive](/reports/archive).

Read-only users see **View** and **View Automations** only.

## Actions from the report header

You don't have to come back to the list to act on the report you're already viewing. The report header carries a **⋮** menu with the same actions — **Duplicate**, **Save As Template**, **View Automations** and **Archive** — minus View and Edit, which the header already has its own controls for.

Both menus are built from one definition, so an action added to the list appears in the header too.