> 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/server/es/concepts/intermediate-concepts/tasks.md).

# Tareas

Las tareas en Devolutions Server son elementos de trabajo asignados a usuarios y vinculados a entradas de bóveda para hacer seguimiento de acciones posteriores como la rotación de contraseñas.

Las tareas en Devolutions Server son elementos de trabajo ligeros que se asignan a usuarios y se vinculan a entradas para hacer seguimiento operativo. Pueden representar acciones como rotar una contraseña, validar una conexión o actualizar la documentación de un sistema concreto.

Dado que las tareas se almacenan de forma centralizada y se asocian al contenido de la bóveda, los equipos obtienen visibilidad sobre lo que hay que hacer y quién es el responsable. Un caso de uso habitual es crear una tarea recurrente vinculada a cuentas privilegiadas para recordar a los propietarios que revisen los accesos o confirmen que la rotación automática funciona como se espera.

#### Temas relacionados

* [Informes](/server/es/web-interface/utilities/reports.md)


---

# 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/server/es/concepts/intermediate-concepts/tasks.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.