> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-dashboard/faqs-y-consideraciones/consideraciones.md).

# Consideraciones

También les resultaría útil a ti y a tu equipo tener en consideración los siguientes puntos:

1. 🍪 **Cookies:** En caso de haber bloqueado o suspendido el equipo, actualizar la página de la consola presionando en el teclado del ordenar control + R o bien, presionar F5. De esta forma se actualiza la página eliminando las cookies del navegador.<br>
2. 🤖 **MacOS:** Activar manualmente la opción de compartir pantalla. Desde mayo del 2020, en Safari de MacOS, es necesario habilitar manualmente los permisos de compartir pantalla desde la configuración de MacOS.<br>
3. 🧭 **Navegador en iOS:** Debes utilizar navegador Safari, ya que los demás navegadores no son compatibles en este sistema operativo.<br>
4. 🕵🏻‍♂️🕵🏼‍♀️ **Navegador:** Para **usar la consola**, te recomendamos **NO UTILIZAR** el navegador en **modo incógnito.**<br>
5. ✅ **Valida tu conexión:** Valida tu conexión en la ventana emergente de la consola de atención.


---

# 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.videsk.io/es-dashboard/faqs-y-consideraciones/consideraciones.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.
