> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/19.latest/model-your-content/content-types-and-structure/backoffice/document-blueprints.md).

# Document Blueprints

Learn how to create and use Document Blueprints in Umbraco.

{% hint style="info" %}
Document Blueprints were previously called Content Templates.
{% endhint %}

## Document Blueprints Overview

A Document Blueprint allows editors to preconfigure a content node. It serves as a reusable starting point when creating new content.

Document Blueprints are managed in the **Library** section. To work with them, a user needs access to the **Library** section and access to Document Blueprints (all or a start node). For more information, see the [Access to Document Blueprints](#access-to-document-blueprints) section.

### Method 1 – Create a Document Blueprint from the Content Section

{% hint style="warning" %}
Before using this method, make sure you have already [created some content](/umbraco-cms/19.latest/model-your-content/content-types-and-structure/data/defining-content.md#3-creating-the-content).
{% endhint %}

1. Go to the **Content** section and select an existing content node.
2. Click the **...** menu next to the node and choose **Create Document Blueprint**.

![Action Button](https://1643013459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjUVOXg32RETcw042xPpN%2Fuploads%2Fgit-blob-dd6e2f5b63dc0508720ed8e91e72931455dc2139%2Faction-menu-DB-18.png?alt=media)

3. Enter a **Name** for the new blueprint.

![Document Blueprint Name Field](https://1643013459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjUVOXg32RETcw042xPpN%2Fuploads%2Fgit-blob-4702f8217481b75252366770a438393ea71395a4%2FName-Content-Template-DB-19.png?alt=media)

4. Select the **Destination** folder for the blueprint.
5. Click **Save**.

The new blueprint appears in the selected folder of the **Document Blueprints** tree in the **Library** section.

![New Document Blueprint](https://1643013459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjUVOXg32RETcw042xPpN%2Fuploads%2Fgit-blob-513518f0659601b1baca341b0379349ed1a8e228%2FFind-Content-Template-DB-19.png?alt=media)

{% hint style="info" %}
If you don’t see the new blueprint, try refreshing your browser.
{% endhint %}

### Method 2 – Create a Document Blueprint from the Library Section

1. Go to the **Library** section.
2. Click the **...** menu next to the **Document Blueprints** tree, or next to a folder within it.
3. Select **Create...**.

![Create Document Blueprint](https://1643013459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjUVOXg32RETcw042xPpN%2Fuploads%2Fgit-blob-4ed22575df06847efad3741a05078f363632d0b0%2FCreate-Content-Template-DB-19.png?alt=media)

4. Choose the Document Type you want to base the blueprint on.

![Select Content Type](https://1643013459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjUVOXg32RETcw042xPpN%2Fuploads%2Fgit-blob-6881e02bfbe87feb77875f30673f38218225e414%2FContent-Type-DB-19.png?alt=media)

{% hint style="warning" %}
You can only create Document Blueprints from **Document Types** or **Document Types with Templates**. Element Types are not offered.
{% endhint %}

5. Enter a **Name** for the blueprint.
6. Click **Save**.

The new blueprint appears in the folder you selected in the **Document Blueprints** tree.

### Edit a Document Blueprint

To edit an existing Document Blueprint, follow these steps:

1. Go to the **Library** section.
2. Open the **Document Blueprints** tree.
3. Select the blueprint you want to edit.
4. Make your changes.
5. Click **Save**.

### Use a Document Blueprint

Once you have created a Document Blueprint, you can use it to create new content nodes.

{% hint style="info" %}
Document Blueprints can only be selected when creating a new content node. They cannot be applied to existing content.
{% endhint %}

To use a Document Blueprint, follow these steps:

1. Go to the **Content** section.
2. Click **+** on the root node and select **Create**.

![Create From Template](https://1643013459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjUVOXg32RETcw042xPpN%2Fuploads%2Fgit-blob-9d0654d7bb15f33b5c28ebbc67b12c508ca619a9%2FCreate-From-Template-DB-18.png?alt=media)

3. Select the **Document Type** that has an associated blueprint.
4. Choose how to create the new content:
   * Use the Document Blueprint
   * Start with a blank node

![Select Template](https://1643013459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjUVOXg32RETcw042xPpN%2Fuploads%2Fgit-blob-8894cb23d5e19b4e0b065bb0877830ae7610715d%2FSelect-Template-DB-19.png?alt=media)

## Access to Document Blueprints

Access to Document Blueprints is configured on User Groups and Users, in the same way as for documents, media, and elements.

* **Allow access to all document blueprints**: The user can manage every Document Blueprint and folder.
* **Document blueprint start node**: The user can only manage the Document Blueprints within the selected folder. A User Group has one start node, while a User can have more than one. Folders above a start node are shown but cannot be selected.

Within their start node, a user can create, edit, move, and delete Document Blueprints and folders. A user without any Document Blueprint access does not see the **Document Blueprints** tree.

To create a Document Blueprint from the **Content** section, a user also needs the **Create Document Blueprint** document permission. Without Document Blueprint access, the action shows a message that the user does not have access.

On new installs, the **Administrators** and **Editors** User Groups have access to all Document Blueprints. For upgraded sites, see the [Breaking Changes Overview](/umbraco-cms/19.latest/get-started/upgrading-and-migrating/version-specific.md) article.

For more information, see the [Users](/umbraco-cms/19.latest/manage-and-publish-content/users-and-members/users.md) article.

## Restricting the Document Types for Document Blueprints

As an implementer or package creator, you can limit which Document Types appear when you create a Document Blueprint. Use the `FilterAllowedForBlueprintsAsync` method of a Content Type Filter.

For more information, see the [Filtering Allowed Content Types](/umbraco-cms/19.latest/extend-your-project/server-side-extensions/content-type-filters.md) article.


---

# 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.umbraco.com/umbraco-cms/19.latest/model-your-content/content-types-and-structure/backoffice/document-blueprints.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.