> 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-heartcore/getting-started/backoffice-users-and-api-keys.md).

# Backoffice Users and API Keys

Managing Umbraco Heartcore Users and API keys

In this article you will learn how to add Users to the backoffice and how to manage the API Keys.

## The Backoffice User

A Backoffice user can be added in two ways.

* Added from the portal from the Team Management section, or
* From the Users Section in the Backoffice

A feature that is unique for Umbraco Heartcore is the option to create an API Key for specific users. The API Key can be created from the API Key section of the User page. This page can be found under the Users Section in the top-left navigation of the backoffice.

![User Page in the Backoffice](https://3751537080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fad8WDpzCbd6plrNqe51p%2Fuploads%2Fgit-blob-be5ec581b6b250dbc9c4e8ac14edda5be58ca141%2FuserAPI.jpg?alt=media\&token=55bb3a7e-6e23-40e1-b1c8-28e5f59e117a)

## API Keys

By default, the Content Delivery API is public, if you would like to protect it you can do so in the "Settings" section and "Headless" tree.

![Protect API](https://3751537080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fad8WDpzCbd6plrNqe51p%2Fuploads%2Fgit-blob-8bbda789e216385e31482fb71b37410f30bb7463%2FheartcoreAPIprotect.png?alt=media\&token=8c88d922-bc07-4819-9be5-edcf8fe027d2)

If your Content Delivery API is protected or you want to use Content Management APIs, your user will need to have an API Key assigned. When you have navigated to the Users section mentioned above you can create the API Key by clicking the "Create API Key" button.

A modal will pop up where you enter the name of the key and set a date for when it should expire. If there is no expire data, the API Key will be valid until you delete it manually.

![Creating the API Key](https://3751537080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fad8WDpzCbd6plrNqe51p%2Fuploads%2Fgit-blob-e0081efc9deaabf4dfd57e317eae89e07c8c5879%2FcreateAPI.png?alt=media\&token=3faf2693-ae0d-44c0-acdc-9c674d3493db)

Once the API Key has been created you will see the actual key and two examples on how to use the key with the Authorization header and an API-Key header.

![The created API Key](https://3751537080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fad8WDpzCbd6plrNqe51p%2Fuploads%2Fgit-blob-770d1809c965247afab60803176ed6a4204c2eac%2FgeneratedAPI.png?alt=media\&token=78d6ba57-80be-4a12-96ad-859b9577173f)

You are able to see a list of all your created API Keys and all relevant information. You are also able to revoke a generated key.

![List of all APIs](https://3751537080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fad8WDpzCbd6plrNqe51p%2Fuploads%2Fgit-blob-fa49005b61127279f708c2b87d49a8fd58c26276%2FlistOfAPIs.png?alt=media\&token=d8036e87-1a59-4561-9674-22b511dd3617)

{% embed url="<https://www.youtube.com/embed/QHrFcEibYrE?rel=0>" %}
Umbraco Heartcore: API keys
{% endembed %}


---

# 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-heartcore/getting-started/backoffice-users-and-api-keys.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.