> 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/pdso-management/pdso-data-sources/pdso-import-a-data-source.md).

# Importing a data source

If your role allows it, you can import a data source into Data Optimizer.

Perform the following steps to import a data source:

1. On the **Menu**, click **Management**.

   The Manage Your Environment page opens.
2. On the **Data Sources** card, click **Import Data Source**.

   The Import Data Sources page appears with a list of discovered data sources from Data Catalog.
3. Select the data source(s) that you want to import.
4. Click **Import**.

   A message confirming that the data source was mounted appears at the top of the page.

The data source is mounted in Data Optimizer.


---

# 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/pdc-10.2-data-optimizer/pdso-management/pdso-data-sources/pdso-import-a-data-source.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.