> 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/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi/connect-to-a-pentaho-repository.md).

# Connect to a Pentaho Repository

Once a repository is created, a menu appears next to the **Connect** link. You can use this menu to connect to the repository.

**Note:** If you are in the process of creating your first repository, select **Connect Now** and then begin the procedure at Step 2.

1. Select a repository in the **Connect** menu.
2. Log on to the repository by entering your **User Name** and **Password** credentials. For example, **User Name** = `admin`, **Password** = `password`.
3. Click **OK** to exit the Repository Configuration dialog box.

   Your user name and repository display name will appear in the upper right corner of the PDI client toolbar.

   **Note:** If you want the Repository Connection window to automatically appear when the PDI client starts, go to **Tools** > **Options** and click **Show repository dialog at startup**.


---

# 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/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi/connect-to-a-pentaho-repository.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.