> 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/pentaho-analyzer-cp/set-analyzer-report-options/set-default-report-options.md).

# Set default report options

As an administrator, you can add default report options that are applied whenever a new report is created. Adding default report options does not apply the changes to existing reports. You can modify the options on reports without affecting the default option settings. You can also set an existing report back to the default settings by clicking the **Reset to default** link on the **Other** tab of the **Report Options** dialog box.

Role permissions are as follows:

| Actions | Administrator | Power user | Business analyst (View-only) |
| ------- | ------------- | ---------- | ---------------------------- |
| Set     | X             |            |                              |
| Reset   | X             | X          |                              |
| Remove  | X             |            |                              |

Perform the following steps to set a default report option:

1. Open the report you want to modify.
2. Select the **More actions and options** button, then click **Report Options**.

   The **Report Options** dialog box displays.
3. Enter the new default options in the **Report Options** dialog box and select **Set as default for all reports**.

   The **Alert** dialog box displays and gives you the option of canceling your changes.
4. Click **OK** to apply your new defaults.

   The default options are set for new reports.

   **Note:** Default settings cannot be applied to the dimensions that are available on the **Drill-Through Columns** dialog box.


---

# 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/pentaho-analyzer-cp/set-analyzer-report-options/set-default-report-options.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.