> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/account-management/organization-management/organization-settings/organizational-templates.md). # Organizational Templates Create reusable exclusion reason sets, tag hierarchies, and protocols for organization-owned nests. **Organizational Templates** store reusable exclusion reason sets, tag hierarchies, and protocols. Use them when several organization-owned nests need the same starting structure. {% hint style="info" %} Templates are available only to nests owned by your organization. Check the owner in [Nest Settings](/your-nests/nest-settings.md). {% endhint %} ### Create A Template 1. In the user menu, select **Organizations**. 2. Select your organization, then select **Templates**. 3. Select **Exclusion**, **Tagging**, or **Protocol**. 4. Select **Add Template**. 5. Enter a **Name** and optional description, then select **Create**. 6. Select the template title to configure it.
The Organizations page with Templates selected in the navigation.

Select Templates from your organization.

### Configure A Template Choose the template type that matches the structure you want to reuse.
Exclusion Reasons An exclusion template stores a reusable set of screening exclusion reasons. 1. Open the exclusion template. 2. Select **Add**. 3. Enter an exclusion reason, then select **Add**. 4. Use the arrow controls to nest reasons under a parent reason. 5. Use the pencil or trash icon to edit or delete a reason.
An exclusion template showing a hierarchy of exclusion reasons and arrow controls.

Arrange exclusion reasons into a hierarchy.

Nested reasons remain available during screening and appear in the PRISMA output. For exclusion-reason guidance, see [Configure Screening](/review-workflow/screening/configure-screening.md).
Tagging A tagging template stores a reusable tag hierarchy. A tag is the core unit of data capture. It can hold a datapoint or a set of datapoints. Create the hierarchy from scratch, or import it from an organization-owned nest. 1. Open the tagging template. 2. To create tags, add and arrange them as you would in a nest.
A tagging template showing a tag hierarchy in the editor.

Build and arrange tags in the template editor.

3. To import a hierarchy, select **Import from nest**. 4. Select a nest, then select **Import**. 5. To import one branch, select its root tag, then select **Import from Root Tag**.
The Import from nest dialog with a nest selected for importing its tag hierarchy.

Import a tag hierarchy from an organization-owned nest.

If you need several branches, import the hierarchy and remove unneeded tags. For tag-structure guidance, see [Configure Tag Hierarchy](/review-workflow/tagging/configure-tagging.md).
Protocol A protocol template stores reusable headings, tables, and text for **Nest Home**. 1. Open the protocol template. 2. Write in the editor or paste an existing protocol. For protocol setup guidance, see [Nest Setup](/review-workflow/nest-setup.md).
A protocol template open in the editor with headings, tables, and text.

Create reusable protocol content in the editor.

### Import A Template Into A Nest Each template appears only in organization-owned nests. * **Exclusion:** On **Configure Screening**, select **Import** and choose the template. * **Tagging:** On **Configure Tag Hierarchy**, select **Configure** → **Initialize** → **From Template**. * **Protocol:** On **Nest Home**, select the three vertical dots, then select **Templates**. See [Configure Screening](/review-workflow/screening/configure-screening.md), [Import Tag Hierarchies](/review-workflow/tagging/configure-tagging/import-tag-hierarchy-templates.md), and [Project Setup](/review-workflow/nest-setup.md) for the full workflows.
The template import options in a nest, including exclusion, tagging, and protocol templates.

Import templates into an organization-owned nest.

### Manage Templates The template list shows how many organization-owned nests use each template. It doesn't link to those nests. * To rename a template, select the pencil icon next to its title. * To delete a template, select the trash icon next to its title. ### See Also
:share-nodes:
Sharing and Access		Share a nest with people and organizations.Sharing and Access
:gears:
Organization Settings		Manage organization details, members, templates, and billing.Organization Settings
--- # 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.nested-knowledge.com/account-management/organization-management/organization-settings/organizational-templates.md?ask=&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.