> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/guest/es/configuracion/guest-sites/guest-visit-actions.md).
# Acciones de visita de Guest
Gestiona los registros de visitas en Guest
Verkada Guest ofrece a los administradores varias opciones para gestionar los datos de visitas, incluyendo añadir notas, marcar a un visitante como persona de interés, ocultar grabar de visitas o eliminar permanentemente los datos de la visita.
***
## Acciones de Guest
{% hint style="danger" %}
Necesitas al menos **Visor del sitio Workplace** permisos para gestionar Acciones de Guest.
{% endhint %}
### Añadir notas
{% stepper %}
{% step %}
**En Verkada Command, ve a All Products > Workplace >** 
**Guest.**
{% endstep %}
{% step %}
**Selecciona la visita del registro de Guest.**
{% endstep %}
{% step %}
**En los detalles de la visita, selecciona Acciones > Añadir notas.**
{% endstep %}
{% endstepper %}
### Marcar como persona de interés
{% stepper %}
{% step %}
**En Verkada Command, ve a All Products > Workplace >** **Guest.**
{% endstep %}
{% step %}
**Selecciona la visita del registro de Guest.**
{% endstep %}
{% step %}
**En los detalles de la visita, selecciona Acciones > Marcar como persona de interés.**
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
Consulta [Crear una persona de interés](/verkada-cameras/es/analiticas/people-analytics/create-a-person-of-interest.md) para más información.
{% endhint %}
### Imprimir credencial
{% hint style="warning" %}
Solo verás esta opción si tienes una impresora en línea en el sitio de Guest.
{% endhint %}
{% stepper %}
{% step %}
**En Verkada Command, ve a All Products > Workplace >** **Guest.**
{% endstep %}
{% step %}
**Selecciona la visita del registro de Guest.**
{% endstep %}
{% step %}
**En los detalles de la visita, selecciona Acciones > Imprimir credencial.**
{% endstep %}
{% endstepper %}
### Ocultar visita
La acción Ocultar visita elimina un grabar de Command, pero sigue siendo recuperable mediante exportaciones o la API.
{% stepper %}
{% step %}
**En Verkada Command, ve a All Products > Workplace >** **Guest.**
{% endstep %}
{% step %}
**Selecciona la visita del registro de Guest.**
{% endstep %}
{% step %}
**En los detalles de la visita, selecciona Acciones > Ocultar visita.**
{% endstep %}
{% endstepper %}
### Eliminar visita
{% hint style="danger" %}
Necesitas **Administrador de la organización** permisos para eliminar una visita en Guest.
{% endhint %}
{% stepper %}
{% step %}
**En Verkada Command, ve a All Products > Workplace >** **Guest.**
{% endstep %}
{% step %}
**Selecciona la visita del registro de Guest.**
{% endstep %}
{% step %}
**En los detalles de la visita, selecciona Acciones > Eliminar visita.**
{% endstep %}
{% step %}
**En la ventana de confirmación, selecciona Eliminar permanentemente.**
{% endstep %}
{% endstepper %}
---
# 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://help.verkada.com/guest/es/configuracion/guest-sites/guest-visit-actions.md?ask=&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.
