> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/dashboards.md).

# Dashboards

Dashboards let you build views of your evidence from familiar fields, without defining data sets, and turn them into PDF reports on demand or on a schedule. Every dashboard reads read-only evidence with your own access, and every chart and table opens the records behind it.

Open **Dashboards** in the sidebar. Its pages, **Your dashboards**, **Scheduled reports** and **Report history**, are also tabs at the top of each page.

| Page                                                                                                                           | What it covers                                                                                                                               |
| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
| [Your Dashboards](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/dashboards/your-dashboards.md)     | Open starter and custom dashboards, create and customize your own, build your own widgets, filter them, export a PDF and ask AI for a brief. |
| [Scheduled Reports](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/dashboards/scheduled-reports.md) | Generate a PDF of a dashboard once or on a recurring schedule, kept in Report history and emailed if you choose.                             |
| [Report History](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/dashboards/report-history.md)       | Download generated PDFs, check their scope and retry failed ones.                                                                            |

{% hint style="warning" %}
You need a role that can view, create or update dashboards to see **Dashboards** in the sidebar. Creating dashboards, scheduling reports and changing report branding each need their own permission; buttons you cannot use are not shown.
{% endhint %}

## Evidence Sources and Scope

Every dashboard uses the same scope bar:

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F0vqWSz3IgqFX1IPT0iPm%2Fv2-dash-scope.png?alt=media&amp;token=e1af8a1d-eb9a-4e32-8200-29bb4872b0fc" alt="Dashboards tabs and the scope bar with evidence source, application records, platform, organization, environment and activity window"><figcaption></figcaption></figure>

| Control                 | Options                                                                                                  |
| ----------------------- | -------------------------------------------------------------------------------------------------------- |
| Evidence source         | **IZ Suite evidence (live, your access)**, or **Commerce · sample scenario** (illustrative sample data). |
| **Application records** | **All application records**, **Mule runtime applications** or **Code repositories**.                     |
| **Platform**            | **All platforms**, or one platform (for example AWS, Azure AIS, Code, MuleSoft).                         |
| **Organization**        | **All organizations**, or one organization.                                                              |
| **Environment**         | **All environments**, or one environment.                                                                |
| **Activity window**     | **All time**, **Last 7 days**, **Last 30 days** or **Last 90 days**.                                     |

Below the bar, IZ Suite shows when the evidence was read and how many application versions are in scope. Posture always uses the latest assessment; the activity window applies to activity such as completed assessments. Click **Refresh evidence** to read it again.

At the bottom of each dashboard, a list of evidence notes explains what the numbers count, for example that application counts are application/version records and that monitor status is the last recorded check, not an availability percentage.

## Next Steps

* [Your Dashboards](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/dashboards/your-dashboards.md): start from a starter dashboard.
* [Report History](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/dashboards/report-history.md): download the PDFs you generated.
* [Scheduled Reports](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/dashboards/scheduled-reports.md): get a PDF before every review.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/dashboards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
