> For the complete documentation index, see [llms.txt](https://help.chartplugin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.chartplugin.com/manage-charts-style/using-a-template.md).

# Using a Template

Templates capture the entire Style tab configuration—colours, typography, even per-chart-type tweaks. They make it easy to share design language across your team. One template contains styles for all chart types.

### Templates

Access the Templates via the plugin menu and manage it:

* **List view** — shows every template.
* **Reorder** — click Make default; the first template becomes the default.
* **Delete** — removes a template. You’ll be asked to confirm.
* **Copy** — duplicate a template to experiment safely.

### Collaboration tips

* Use consistent naming conventions (e.g. `Dept - Use Case`).

### Troubleshooting

| Issue               | Fix                                                                                                   |
| ------------------- | ----------------------------------------------------------------------------------------------------- |
| Template list empty | Sign in or re-enter your license key in the Create chart UI.                                          |
| Cannot save         | Ensure your license email is set and template service is reachable. Check the Critical Errors banner. |


---

# 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://help.chartplugin.com/manage-charts-style/using-a-template.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.