> 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/master.md).

# Work Manager

En esta sección encontrará muchas explicaciones y vídeos que le enseñarán a utilizar el software Work Manager de Enate para gestionar los procesos de su empresa día a día..

### Descripción general de Work Manager

Work Manager es una aplicación web multipágina que utilizan los miembros del equipo de prestación de servicios para gestionar Tickets, Casos y Acciones en progreso en el marco de los procesos de negocio gestionados.

Los usuarios de Work Manager son agentes de servicio, jefes de equipo, responsables de operaciones y directivos. Work Manager ofrece un conjunto estándar de vistas que permiten a estos usuarios realizar su trabajo.

Vea este vídeo para obtener una breve descripción general de Work Manager:

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

### Compatibilidad con navegadores

El *Work Manager* está diseñado para admitir los siguientes navegadores:

* Última versión de Chrome (en el momento de salida)
* Última versió n de Firefox (en el momento de salida)
* Última version de Microsoft Edge, basado en Chromium (en el momento de salida)


---

# 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/master.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.