> 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-2/check-the-updated-connection-settings-page.md).

# Check the Updated Connection Settings Page

Preview your updated Pandium connection settings by building a new release, updating the tenant on the Latest channel, and confirming the new dynamic configs appear before their options have been sync

You just added new elements to the PANDIUM.yaml, which controls the Connection Settings page. Let's take a look at that those configs for your tenant!

Before you can see the results of your updated PANDIUM.yaml on the *Connection Settings* page you will need to put your tenant on a new release based on your new code.

1. Follow all the steps in [Check the Customized Connection Settings Page](/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/write-the-integration-in-typescript/check-the-customized-connection-settings-page.md).

<figure><img src="https://4017407078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MfJn-9R_dn6dvcGNcdk%2Fuploads%2FpcCK9aqZksMgdG88qeMN%2Fimage.png?alt=media&amp;token=cf51416c-ddf9-456a-933f-c08ee061962e" alt=""><figcaption></figcaption></figure>

4. When you click **Settings** for your tenant the *Connection Settings* page will be displayed. Since your release channel is *Latest* the tenant has been automatically updated to the new release you just made.

<figure><img src="https://4017407078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MfJn-9R_dn6dvcGNcdk%2Fuploads%2FcBhEJztPU810C5BkyuE8%2Fimage.png?alt=media&amp;token=9966a45d-b2d4-4cd2-94c4-2b9d601407fb" alt=""><figcaption></figcaption></figure>

The new configurations are present! But they are disabled and show as unsynced, because the tenant's metadata doesn't have any `pokemon_types` or `slack_users` yet. Those options will be fetched from each API and saved to metadata during the init sync.

So the next step is to write that init sync flow!


---

# 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.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-2/check-the-updated-connection-settings-page.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.