> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.3/vizpads-explore/anomaly-management-for-line-charts/vizpad-level.md).

# Vizpad level

Control anomaly visibility at the Vizpad level by enabling or disabling anomalies in View or Edit mode without affecting instance-wide settings.

{% hint style="warning" %}
Enabling/disabling anomalies in Vizpads level will not change the instance level settings configured in **Application Settings**.
{% endhint %}

### **View mode**

1. Click on the required Vizpad from **Explore** tab.
2. On the top panel, you can find an array of icons. The first icon allows you to enable/disable anomalies for the current Vizpad.

<figure><img src="https://content.gitbook.com/content/M1pa9Nct9EmVU4Ol8Mol/blobs/dTtQo9cNjX6zQgkfrIRi/image.png" alt="" width="563"><figcaption><p>Setting anomalies for a Vizpad in View mode</p></figcaption></figure>

3. If the icon is enabled (blue in color), then anomalies will be displayed for line charts in the Vizpad.
4. Click on the icon to show/hide anomalies as required. Everytime the button is clicked, a message will be displayed on the top of the screen informing whether the anomalies are enabled/disabled.

### **Edit mode**

1. Click on the **Edit** button on the required Vizpad.
2. On the top right corner, click on the **Settings** icon. If **Enable Anomalies** toggle is enabled, then anomalies will be displayed for line charts. If the toggle is disabled, then the anomalies will be hidden.

<figure><img src="https://content.gitbook.com/content/M1pa9Nct9EmVU4Ol8Mol/blobs/YX1pJETAHFZO3HRJjy7u/image.png" alt="" width="563"><figcaption><p>Setting anomalies for a Vizpad in Edit mode</p></figcaption></figure>


---

# 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://help.tellius.com/tellius-6.3/vizpads-explore/anomaly-management-for-line-charts/vizpad-level.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.