> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/write-the-integration-in-typescript/check-the-customized-connection-settings-page.md).

# Check the Customized Connection Settings Page

You just customized the PANDIUM.yaml, which controls the Connection Settings page. Let's take a look at that updated page for your tenant!

1. Commit your code and push it to your remote repository.
2. On the Integration Hub navigate to your integration by clicking **Integrations** from the side bar > the **Unpublished** tab > the card for your *Pokémon of the Day* integration. This will display the integration details page.

<figure><img src="/files/gjdEuJe7Pipb11dVrcRV" alt=""><figcaption></figcaption></figure>

3. Click **Build Release**. This will open the *Manually build a new Release* dialog box.

<figure><img src="/files/fIq70i3Rn7syev7wqtc1" alt=""><figcaption></figcaption></figure>

4. Enter a tag for the new release; this should be something to remind you what features have been added in this release.
   * If the source control tenant is currently running the **Build Release** button will be disabled. It will be enabled when the source control run is complete.
5. Click **Build Release.**
   * This will display the *Source Control* tab of the *Admin Settings* page and kick off a run of your [source control](/reference/source-control.md) tenant.
   * That run will generate a new release of your integration based on the code you just pushed to your remote repository.
6. When the source control run is complete, navigate back to your integration's detail page by clicking **Integrations** from the side bar > the **Unpublished** tab > the card for your *Pokémon of the Day* integration.
7. Click the **Tenants** tab. This will display a list of your integration's tenants. Right now there should be one.

<figure><img src="/files/KpUhIflJYOILPg30xJER" alt=""><figcaption></figcaption></figure>

8. Click on your tenant. This will display the *Tenant Detail* page.

<figure><img src="/files/9gBuwfQVjaeUha9sHAnn" alt=""><figcaption></figcaption></figure>

9. Click **Settings**. This will display the *Connection Settings* page. Since your release channel is *Latest* the tenant has been automatically updated to the new release you just made.

<figure><img src="/files/05b1hYWMsE1vhZgqnwls" alt="" width="375"><figcaption></figcaption></figure>

Now, the connections setting page doesn't have any unnecessary options!


---

# 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.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/write-the-integration-in-typescript/check-the-customized-connection-settings-page.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.