> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/espanol/trabajar-con-elementos-de-trabajo-enlazados.md).

# Trabajar con Elementos de Trabajo Enlazados

Varias funciones de Enate le permiten gestionar las actividades que realizan diferentes equipos, permitiéndole crear y supervisar fácilmente las tareas, incluso cuando no tiene todos los permisos para las tareas de los demás.

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM2MTg5NQ==>" %}

Puede:

* crear y enlazar tareas, incluso en áreas de negocio para las que no tiene permisos;
* compartir y añadir comunicaciones entre esas tareas.

Al lanzar un Caso o un Ticket desde uno ya existente, se crea una relación "Enlazada" entre las tareas. Las tareas creadas de este modo mantendrán un enlace con el Caso o Ticket original y se mostrarán en una [pestaña de "Enlaces"](/enate-help/espanol/trabajar-con-elementos-de-trabajo-enlazados.md#visualizar-las-tareas-enlazadas-la-pestana-de-enlaces) dentro de ellas, lo que facilita el seguimiento de un grupo de tareas que se relacionan entre sí.

Echemos un vistazo a algunas de estas funciones, empezando por la forma de crear Tareas enlazadas...


---

# 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.enate.net/enate-help/espanol/trabajar-con-elementos-de-trabajo-enlazados.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.