> For the complete documentation index, see [llms.txt](https://vampauth.gitbook.io/vampauth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vampauth.gitbook.io/vampauth-docs/features/key-groups.md).

# Key groups and payload routing

Use groups when different keys should receive different scripts, such as standard and premium editions.

1. Create a group in the project.
2. Assign its payload loader from the same project.
3. Assign keys to the group, or select it on a provider package for new keys.
4. Test the shared loader URL with a key from each group.

Group names are sanitized and limited to 30 characters. Colours use six-digit hex values.

## Default payload

Set a project default for ungrouped keys. Without an applicable override, the loader URL's own script is the fallback. Routing settings don't create new keys.

The loaded script reads the exact group name from `VAMPAUTH.key_group`. Ungrouped and keyless runs use `nil`.

Deleting a group keeps its keys as ungrouped and detaches package mappings. Check the default payload before deleting a group used for paid access.

## Next steps

* [Groups and default payload](/vampauth-docs/api-reference/management/groups.md)
* [Runtime variables and helpers](/vampauth-docs/development/loader-macros.md)


---

# 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://vampauth.gitbook.io/vampauth-docs/features/key-groups.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.