> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/10.2-analytics/pentaho-analyzer-cp/adding-filters-to-an-analyzer-report/add-a-default-filter.md).

# Add a default filter

As an administrator, you can add a default filter to Analyzer reports that is applied whenever a new report is created. This prevents users from adding large dimensions to reports that can impact server performance. Adding a default filter eliminates the step of having to add filters to each dimension to your report that you want filtered. Default filters are not applied to existing reports.

Perform the following steps to add a default filter to a report:

1. Add the filter(s) that you want to set as default to your report.
2. Click **More actions** and options and choose **Default Filters** > **Set for New Reports**.

   Other options are **Remove for New Reports** and **Reset to default.**

   The Alert dialog box displays.
3. Click **OK** to close the dialog box and set the default filters.

New reports based on the report you have modified will have the default filters applied. The **Remove for New Reports** command removes the filters for new reports. The **Reset to default** command removes any filters you have added to a report and sets the report back to the default filters.

**Note:** Filters that are added to a report in the chart view will display in the filters workspace, but are not saved in the default filters.


---

# 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://docs.pentaho.com/pba/10.2-analytics/pentaho-analyzer-cp/adding-filters-to-an-analyzer-report/add-a-default-filter.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.
