> 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/model-your-content/content-types-and-structure/data/defining-content/elements.md).

# Elements

Learn how to use Elements to add reusable content to your website.

Instead of replicating the same content on a per-page basis, Elements allow you to create reusable content. By creating your content once, you can reuse it across as many pages and documents as you need.

Elements are ideal for call-to-action blocks, banners, and other shared content that appears across multiple pages.

{% hint style="info" %}
Elements hold one piece of content that's shared and centrally updated everywhere it's referenced. If you instead need editors to compose different content per page from a set of block types, use the [Block List Editor](/umbraco-cms/model-your-content/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md) instead.
{% endhint %}

## Library

Elements are managed from the Library section in the Umbraco Backoffice.

The Library section is a central editorial hub for reusable content. By default all user groups except Sensitive data and Translators have access to the section.

{% hint style="info" %}
If the project was started on versions before Umbraco 18, only the Administrators user group has access to the Library section.

Manage permissions to the Library section from the Users section in the Umbraco backoffice.
{% endhint %}

## Manage Elements

Elements are configured in the Settings section and managed from the Library section. They are referenced in your content using the Element Picker property.

### Build and Configure Elements

Elements are created as Element Types in the Settings section of the Umbraco backoffice. As with all Element Types, Elements are not routable and are not attached to a Template.

Toggle the **Allow in Library** option on the Structure Workspace View to turn your Element Type into an Element.

![Element Type Structure tab with Allow in Library toggled](https://1282852327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbFfxUcTsPCzuMkpCkZsT%2Fuploads%2Fgit-blob-dbd083dda6ced76359e0288353ff2ce626a00982%2Felements-allow-in-library.png?alt=media)

You can add groups, tabs, and properties like you would to any other Element and Document Type.

Since your project will contain different Document Types, group your Elements into a dedicated folder to keep your workspace organized.

### Create Elements

With your Element configured, you can start using it to create reusable content in the Library section.

1. Click the **+** icon.
2. Select which Element Type you want to base the Element on.
3. Fill in the relevant properties.
4. **Save** or **Save and Publish** once the content is ready.

![The Library section with an Element selected](https://1282852327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbFfxUcTsPCzuMkpCkZsT%2Fuploads%2Fgit-blob-dade2eb0a2e7f7e1eee96cf1fa366bbc235611d0%2Felements-library-section.png?alt=media)

To maintain an overview of your reusable content, it can be a good idea to use folders for organizing the content in your Library.

Use the **Info** workspace view to find relevant details about the element, such as history and where the element is used.

![Element Type Structure tab with Allow in Library toggled](https://1282852327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbFfxUcTsPCzuMkpCkZsT%2Fuploads%2Fgit-blob-1b898d324612bcc82aba561e61c0c46b7fc7eb28%2Felements-info-workspace-view.png?alt=media)

### Use Elements

Once you have created the elements in the Library section, they can be referenced anywhere an Element Picker has been configured.

![Element Type Structure tab with Allow in Library toggled](https://1282852327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbFfxUcTsPCzuMkpCkZsT%2Fuploads%2Fgit-blob-12c5274ae7a9f0307d59ff646d43f7968de833a0%2Felement-added-to-content.png?alt=media)

You can add elements to your content in the Content section using an Element Picker. This needs to be added as a property on the Document Type. Read the [Element Picker](/umbraco-cms/model-your-content/property-editors/built-in-umbraco-property-editors/element-picker.md) article to learn more about how to use and configure it.

{% hint style="info" %}
Elements and Blocks (used by the Block List and Block Grid editors) don't mix within the same property. A Block List or Block Grid always stores its block content inline. It cannot be configured so that a block type is either inline content or a reference to a Library Element. To combine both approaches on one page, add an Element Picker property and a Block List/Block Grid property separately.
{% endhint %}

Making changes to an Element in the Library section, will update all instances of the content throughout the project.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-cms/model-your-content/content-types-and-structure/data/defining-content/elements.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 `build a script that syncs our docs to a CMS` 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.