> 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-user-console/classic-design/about-pentaho-user-console-perspectives/schedules/schedule-reports/manage-schedules/prevent-scheduling-of-a-single-report-or-file.md).

# Prevent Scheduling of a Single Report or File

In the Pentaho User Console, all new reports can be scheduled by default, but as an administrator, you can control which files can be scheduled to run.

1. From the User Console **Home** menu, click **Browse Files**.

   The Browse Files page appears.
2. Browse to the location of a report from the **Browse** pane on the left of the Browse Files page.

   The **Files** pane in the center populates with a list of reports.
3. Click to select the report for which you want to deny scheduling, then click **Properties** in the **Folder Actions** pane.

   The Properties window for that report appears.
4. Click the **General** tab in the Properties window, then unselect the **Allow Scheduling** check box.
5. Click **OK**.

The **Schedule** option next to this report is no longer displayed and the report cannot be scheduled.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pba/pentaho-user-console/classic-design/about-pentaho-user-console-perspectives/schedules/schedule-reports/manage-schedules/prevent-scheduling-of-a-single-report-or-file.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.