> 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-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/change-schedule-owner.md).

# Change schedule owner

You can change the owner of a schedule associated with a user who is no longer active or whose schedule needs to be transferred to someone else.

1. Make sure the followings conditions apply:
   * You must have administrator privileges to change the owner, whether it is a new or existing schedule.
   * The report file must have the right schedule permissions so that an administrator can change the owner.
   * The new owner must have schedule permissions, write permissions on the destination folder, and read permissions on the file.
2. Click the User Console **Home** menu.
3. Select Schedules from the menu.

   The Schedules page opens.
4. Click to select a schedule that was created by the former user.
5. Above the table, click the **Edit Scheduled Task** icon.

   The Edit Schedule wizard opens. If the owner of the schedule is no longer with the organization, a warning is displayed.

   ![Edit schedule wizard](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-f271f1c8a2ef040b20a591e96064b3fbfe5c891d%2FEdit_Schedule_change_owner.png?alt=media)
6. Next to the **Owner** field, click **Change** to change the owner.

   The Change Owner window opens.
7. Click the drop-down in the **New owner** field and select a new user.
8. Click **OK**, then **Next**.
9. In the rest of the wizard, make any changes necessary, click **Next** and then **Finish**.

   A confirmation window appears to confirm the changes.


---

# 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-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/change-schedule-owner.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.
