> 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/pdc-10.2-data-optimizer/pdo-getting-started.md).

# Get started

Data Optimizer integrates with the Pentaho Data Catalog application. After installing Data Optimizer, you are ready to start identifying, classifying, and tiering or purging your files.

You can use Data Optimizer if you are a managed services provider identifying data tiering candidates, a storage administrator reviewing the capacity, utilization, and cost effectiveness of storage, or a backup administrator implementing a disk base solution to increase backup and restore success rates.

To begin using Data Optimizer, you must log in. User authentication, roles, and permissions for Data Optimizer are provided by Data Catalog. Use the login credentials shared by your Data Catalog administrator for access. Navigate to the Data Optimizer application using the **App Switcher**.

View the following articles to guide your use of Data Optimizer:

* [Tour the Home page](https://docs.pentaho.com/pdc-10.2-data-optimizer/pdo-getting-started/tour-of-the-home-page-use-pdc-quick-start.md)
* [Use Data Optimizer](https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-use-data-storage-optimizer.md)
* [Default user roles and permissions in Data Optimizer](https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-management/pdso-rbac.md)


---

# 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/pdc-10.2-data-optimizer/pdo-getting-started.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.
