> 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/configure-the-pandium.yaml.md).

# Configure the PANDIUM.yaml

Customize the connection settings page so it doesn't display options that aren't relevant to the Pokémon Trainer Academy's requests, and declare the tenant metadata the integration will store between

One of the [PANDIUM.yaml](https://github.com/pandium/external-docs/blob/master/build/anatomy-of-an-integration/pandium.yaml-spec)'s key purposes is to populate the *Connections Settings* page which allows users to customize how their [tenant](/getting-started/key-terminology.md#tenant) will run. Another is to declare the [tenant metadata](/getting-started/anatomy-of-an-integration/pandium.yaml-spec/tenant-metadata.md) your integration stores between runs.

Your starter PANDIUM.yaml is on manifest `version: 1.0`, which is the version that supports tenant metadata. Leave that line as it is.

Right now the Pokémon Trainer Academy hasn't asked for any tenant settings, so we just need to remove the unnecessary configurations.

1. Remove `configs` and everything under it from the the PANDIUM.yaml.

The Academy did ask that the integration never repeat a Pokémon. To manage that the integration has to remember which Pokémon it sent last, and tenant metadata is where it will keep that memory. The `metadata_schema` describes the shape of that data: at the end of every run Pandium validates whatever the integration printed to the standard out against this schema and merges it into the tenant's metadata.

2. Replace the properties under `metadata_schema` with a single `last_pokemon_id`.

Your PANDIUM.yaml should now look like this:

```yaml
version: 1.0
base: node:24
build: npm install --production && npm i --save-dev @types/node && npm run build
run: node .
metadata_schema:
  schema:
    name: metadata_schema
    properties:
      last_pokemon_id:
        type: number
```

## Preview the Connection Settings form

You don't need to build a release to see what the PANDIUM.yaml will produce. The Pandium CLI can render the *Connection Settings* form straight from the file on your machine.

3. Run `pandium local preview-configs`. This starts a local server and opens the form in your browser.

Since you removed all the configs, the form should now be empty: none of the starter's options are left. Leave the server running while you work on a PANDIUM.yaml; it reloads the form whenever you save the file, so you can check your changes before you push them. Press Ctrl+C when you're done.

The preview is generated from the file alone, so it doesn't reflect a particular tenant's settings or metadata. For that you'll check the Integration Hub, so let's take a look at how the connection settings page looks with this updated PANDIUM.yaml!


---

# 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-1/write-the-integration-in-typescript/configure-the-pandium.yaml.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.