> For the complete documentation index, see [llms.txt](https://docs.agentsby.yudexlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentsby.yudexlabs.com/conceptos-clave/canales-y-permisos.md).

# Canales y permisos

## Canales

Un agente puede atender por distintos canales, como WhatsApp o webchat. Cada canal tiene su propia configuración de publicación, identidad y reglas de acceso.

## WhatsApp compartido

Si varios agentes usan el mismo número, configura cuál es el agente predeterminado y revisa las reglas de transferencia entre agentes.

## Webchat

Limita los dominios autorizados para evitar que el widget se instale en sitios no controlados. Mantén actualizados el mensaje de privacidad y los campos de contacto.

## Buenas prácticas de seguridad

* Da acceso de edición solo a las personas que lo necesitan.
* No copies contraseñas, tokens ni claves en prompts o documentos.
* Revisa las herramientas externas antes de activarlas.
* Prueba los permisos con una cuenta que no sea administradora.
* Verifica que cada cliente solo pueda consultar sus propios datos.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agentsby.yudexlabs.com/conceptos-clave/canales-y-permisos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.