> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/ctrl/guide/configuration/mytemplates-pre-match/assigning-categories-leagues-and-tournaments-to-a-template.md).

# Assigning Categories, Leagues and Tournaments to a template

{% @storylane/embed subdomain="app" linkValue="uhb9gydaml0u" url="<https://app.storylane.io/share/uhb9gydaml0u>" %}

Once a template has been created and configured, specific categories and tournaments can be added to it. That is, the categories and/or tournaments added will have their settings dictated by the template they are added to. The screenshot below shows Brazilian tournaments (red box) being added to this template.

If a certain category is added this way, it will include only the current available tournaments, not future ones, unless a Category Template is assigned. This is explained in Section 3.8 Tournaments Pre-match.

{% hint style="info" %}
It is also crucial to note that the user must save (green box above) if categories or tournaments are to be added to that template.
{% endhint %}

The ‘non-configured only’ button will quickly show all categories and tournaments that are not currently added to a template and thus require attention if they are to be offered.


---

# 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.sportradar.com/ctrl/guide/configuration/mytemplates-pre-match/assigning-categories-leagues-and-tournaments-to-a-template.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.
