> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/writer/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/writer/admin-guide/configuration-of-writer-templates.md).
# Article Templates Configuration
## Introduction
Previously templates was more or less an empty article. This is no longer the case. Now templates are it's own content type in Open Content and needs to be tweaked for each new setup.
Templates can be either shared with organisation, at the moment this means that all articles created with that template, will be shared with the organisation. This will be changed in version 6.1.1 and forward, but until you have that version the recommendation is to create unit specific templates.
**Organisation wide template:** To be used when you want one template for all users of all units (see earlier paragraph).
**Unit specific template:** This will create new articles, shared with the unit specified in the template.
In each unit specific template, you need to have sharing enabled, like this:
```markup
```
You must change the configuration of the template to suit your organisation and your unit. The actual sharing is done here for the unit in the same way as other objects created in Naviga Creation Tools**.**
**Personal template:** Will be created from the template mentioned above. Personal templates are not shared with anyone, standard rules for OC Groups will be applied.
## Other requirements
Firstly you need Open Content configuration for templates (Content type, extractors and properties).
You then need to make sure that templates are shared with organisation in your OC Group rules.
In our case with unit specific template sharing, the most important is the property above. The unit name needs to be exactly the same name as in Naviga ID, as well as exactly the same name as your OC Import Group Rules. These properties are part of the standard OC Configuration file.
In the Group Rules in Open Content, the template needs to shared with your unit, which can be done by specifying this in the organisation import rule. The Writer will look for a template matching your own unit, so the important thing is that you are allowed to access the template,
## For more in-depth technical information, see our release notes:
### Plugin mounts on bottom bar within the template.
In writer client version 8.2.2, a new key is introduced in config **“enableBottomBarComponents”** to activate the bottom bar plugin within the template.
* Add **“enableBottomBarComponents”: true** in the writer client to mount the bottom bar plugin within the template.
* Add **“enableBottomBarComponents”: false** in the writer client to configuration deactivate the bottom bar plugin within the template.
{% embed url="" %}
---
# 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:
```
GET https://docs.navigaglobal.com/writer/admin-guide/configuration-of-writer-templates.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.