> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/kenai-user-guide/guardian-app/guardian-overview.md).

# The Guardian app

The Guardian app is a browser-based companion to the Kenai dashboard that lets reception and security staff handle visitor tasks on a phone or tablet, on the move, **after** a visitor has signed in at the kiosk. From a visitor's record you can verify their ID, check their declared assets in and out, confirm induction status, and link an access card.

Because it runs in the browser (no app-store install), Guardian is most useful where visitor processing is spread across several staff and devices: instead of everything funnelling through the reception desk, security can pick up ID checks, asset handling, and card linking wherever the visitor is, easing congestion at peak times. Guardian uses the same Kenai sign-in, permissions, and audit trail as the dashboard.

## What you need

* A handheld Android or iOS device, or a tablet, with a camera.
* The latest **Google Chrome** or **Microsoft Edge**.
* Kenai credentials for the site you're working at.
* For asset and induction tasks, the relevant capability (Assets, Induction) enabled on the site.

## Access the app

Open **`guardian.kenai.app`** in Chrome or Edge and sign in.

{% stepper %}
{% step %}

### Go to guardian.kenai.app

In Chrome or Microsoft Edge, open **`guardian.kenai.app`**.
{% endstep %}

{% step %}

### Sign in

On the **Welcome** screen, enter your **Email address** and **Password**, then tap **Continue**. Use credentials linked to the site you're working at.
{% endstep %}

{% step %}

### Select a location

On **Select a location**, choose your site. Guardian opens on the **Visitor Log**.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Tip:** add Guardian to your home screen for one-tap access. Tap the browser **Share** icon, choose **Add to Home Screen**, then **Add**. It then opens full-screen like an app.
{% endhint %}

{% embed url="<https://app.arcade.software/share/0BnUN4qV0n3nKLjqsMsV?embed=true>" %}
Walkthrough: opening Guardian, signing in, and adding it to your home screen.
{% endembed %}

## The visitor log

The **Visitor Log** is Guardian's home screen. It lists everyone who has signed in at the site, each with a live status. Search by name or phone, then tap a visitor to open their **Visitor Profile**.

From the profile you work through the visitor's verification points, each shown as an action tile:

* **Capture ID**: scan and verify the visitor's identification.
* **Assets In** and **Assets Out**: check declared assets in on arrival and out on departure.
* **Link Access Card**: assign a physical entry card.

As you complete each step, the visitor's status chips update live (for example *ID Checked*, *Induction Complete*, *Checked In*, *Access Card*). Once every check is confirmed, the visitor is ready to be granted access.

{% embed url="<https://app.arcade.software/share/G0KRFFvhkWUxJELd0kX0?embed=true>" %}
Walkthrough: finding a visitor and working through their profile in the visitor log.
{% endembed %}

## What you can do

{% content-ref url="/pages/6xlJPosM0u4XPof7DEHE" %}
[Check assets in and out](/knowledge-hub/kenai-user-guide/guardian-app/guardian-assets.md)
{% endcontent-ref %}

{% content-ref url="/pages/lAQ59kMAjHfi2X2qVo8i" %}
[Link an access card](/knowledge-hub/kenai-user-guide/guardian-app/link-cards.md)
{% endcontent-ref %}

{% hint style="info" %}
**Note:** AI-assisted identity verification adds a back-end audit of the operator's ID check.
{% endhint %}


---

# 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.security.gallagher.com/knowledge-hub/kenai-user-guide/guardian-app/guardian-overview.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.