> 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/es/web-interface/administration/management/users/devolutions-cloud-ownership.md).

# Propiedad de Devolutions Cloud

Transfiera la propiedad de Devolutions Cloud a otro administrador e identifique al propietario actual mediante el icono de corona en la lista de usuarios.

En la sección ***Administration – Users***, puede transferir la propiedad de su Devolutions Cloud a otro administrador.

* Para identificar al propietario actual de la instancia de Devolutions Cloud, busque el icono de corona junto al nombre del usuario en la lista de usuarios.
* Para asignar un nuevo propietario, localice el administrador deseado en la lista de usuarios y, a continuación, haga clic en el icono ***Set as owner*** situado junto a su nombre.

{% hint style="info" %}
Solo se permite un propietario a la vez, y únicamente los usuarios con privilegios de administrador pueden ser asignados como propietario.
{% 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/es/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.
