> 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/6.0.2/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 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://docs.navigaglobal.com/newsroom-planner/6.0.2/admin-guide/migration/3.x-4.x/templates.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.