> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/da/web-interface/administration/management/users/devolutions-cloud-ownership.md).

# Ejerskab af Devolutions Cloud

Overfør ejerskabet af Devolutions Cloud til en anden administrator, og identificer den aktuelle ejer via kroneikonet på brugerlisten.

I sektionen ***Administration – Brugere*** kan De overføre ejerskabet af Deres Devolutions Cloud til en anden administrator.

* For at identificere den aktuelle ejer af instansen af Devolutions Cloud skal De se efter kroneikonet ved siden af brugerens navn på brugerlisten.
* For at tildele en ny ejer skal De finde den ønskede administrator på brugerlisten og derefter klikke på ikonet ***Angiv som ejer*** ved siden af navnet.

{% hint style="info" %}
Der kan kun være én ejer ad gangen, og kun brugere med administratorrettigheder kan tildeles som ejer.
{% endhint %}


---

# 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.devolutions.net/cloud/da/web-interface/administration/management/users/devolutions-cloud-ownership.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.