> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/newsroom-planner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/newsroom-planner/4.0-1/admin-guide/migration/3.x-4.x/templates.md).

# Templates

To handle templates for Newsroom Planner, please see the separate documentation for the [Template Handler](https://docs.navigaglobal.com/template-handler/) plugin. The plugin lets you create and edit templates in a simple way. If you have edited your templates in Newsroom Planner 3 or earlier, it's a good idea to save these templates first, using a structured XML Editor, for example Atom.

Templates are chosen in the following order when a user creates a new object or create a personal template: 

1. Personal template, if the user does not have a personal template 
2. Unit template, if there is no unit template
3. Organisation template will be used
4. If there is no Organisation template, Newsroom Planner will not work

{% hint style="info" %}
Templates require OC configuration, documented for the Template Handle plugin
{% endhint %}


---

# 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.navigaglobal.com/newsroom-planner/4.0-1/admin-guide/migration/3.x-4.x/templates.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.