> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/main-dashboard/insights.md).

# Insights

Filter the Insights dashboard by feature and provider instance.

Insights is the dashboard that summarizes your data across providers.<br>

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FklpAqG6TihUct4J3KBzr%2Fimage.png?alt=media&amp;token=32e74898-b98f-4e97-b456-9fb997201a1a" alt=""><figcaption></figcaption></figure>

It can show:

* watchlist
* ratings
* history
* progress
* playlists
* collection

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FYtgSZbMjBS3bgteiNcjT%2Fimage.png?alt=media&amp;token=f574e47e-8da7-4255-a102-f4173b1fec48" alt=""><figcaption></figcaption></figure>

### Why this exists

If you use [Instances](https://wiki.crosswatch.app/crosswatch/settings/connections/instances.md), Insights totals get noisy.

Insights settings let you:

* hide features you don’t care about
* include or exclude specific provider instances from totals

### Choose features and instances

Open **Insight settings** with the gear beside the Insights feature controls.

1. Press the feature buttons to include or exclude features.
2. Tick the provider instances you want in the totals. A provider's main checkbox selects or clears all its instances; a partial mark means only some are selected.
3. Select **Apply changes** to save. Closing the window without applying leaves the saved choices unchanged.

At least one feature stays enabled. If all feature buttons are off when you apply, Watchlist is enabled again.

### Where settings are stored

Settings are stored **in your browser**, not on the server.

If you open CrossWatch in a different browser/device, you’ll get defaults again.

### How instance filtering works

Provider connections are called **Instances** in the UI.

Insights also follows the [main-page profile selection](https://wiki.crosswatch.app/crosswatch/main-dashboard.md#choose-whose-data-to-view). Administrators can choose **Admin** to exclude named instances, or **All profiles** for the combined view. Managed users remain within their assigned scope.

* If you never changed instance selections, Insights includes **all instances allowed by the selected scope**.
* Once you select a provider, Insights aggregates **only those instances**.

New instances are added to your selection automatically.

### Reset

Select **Restore defaults** in Insights settings to select all features and available instances. The reset is pending until you select **Apply changes**. Close without applying to keep your previous settings.

{% hint style="info" %}
This does not change sync pairs or Watcher routes.

It only changes what the dashboard displays.
{% endhint %}

### Related

* Instances: [Instances](https://wiki.crosswatch.app/crosswatch/settings/connections/instances.md)
* API payload used by Insights: [API](https://wiki.crosswatch.app/crosswatch/advanced-and-api/api-reference.md)


---

# 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://wiki.crosswatch.app/crosswatch/main-dashboard/insights.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.
