> 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/17.latest/extend-your-project/server-side-extensions/management.md).

# Management

Details of CRUD operations within Umbraco and how to interact with the data persisted in the database

The intended audience for these reference pages is .NET developers. It is assumed the reader already knows the basics of Umbraco and knows .NET & C#.

{% hint style="warning" %}
Since the release of Umbraco 14, the documentation for Models and Services has been removed from the documentation.
{% endhint %}

## [Models (external)](https://apidocs.umbraco.com/v17/csharp/api/Umbraco.Cms.Core.Models.html)

Find references for the models in the public API. The models include Content, ContentType, Language, Media, and Template classes.

## [Services (external)](https://apidocs.umbraco.com/v17/csharp/api/Umbraco.Cms.Core.Services.html)

Find references for the services available for performing Create, Read, Update, and Delete (CRUD) operations for the models.

### [Learn how to use the Umbraco Services](/umbraco-cms/17.latest/extend-your-project/server-side-extensions/management/using-services.md)

Find a handful of resources for using some of the services available with Umbraco CMS.


---

# 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/17.latest/extend-your-project/server-side-extensions/management.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.