> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/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/command-centre/visitor-management-powered-by-kenai/visitor-management/visitor-directory.md).

# The visitor directory

The visitor directory holds visitor profiles. A profile exists **only** once the visitor has verified a phone number with a one-time PIN. Directories are kept **per location**, not organisation-wide. A visitor who has only visited one site won't appear in another site's directory.

## What's stored

Photo, first name, last name, email, phone, and (if captured) ID number and company. You can customise and save views, as on the other logs.

## What an admin can edit

| Field        | Editable?                                        |
| ------------ | ------------------------------------------------ |
| Name         | Yes                                              |
| Email        | Yes                                              |
| ID number    | Yes                                              |
| Company      | Yes                                              |
| Phone number | **No**, it's the OTP-verified primary identifier |
| Photo        | No                                               |

If a visitor asks to update their details, an admin with directory rights can edit the allowed fields.

## How a visitor updates their own profile

A returning visitor can rebuild their own stored details at the kiosk. The **Remember me to speed up my next check in** toggle normally skips re-verification, so it must be switched off before those details can change:

{% stepper %}
{% step %}

### Switch off Remember me

During the final stage of sign-in, switch the **Remember me to speed up my next check in** toggle off.
{% endstep %}

{% step %}

### Verify with a one-time pin

Enter the one-time pin (OTP) sent to the visitor's mobile number.
{% endstep %}

{% step %}

### Rebuild the profile

On the **REGISTER** form, re-enter or update the details (first name, last name, mobile number, email, company, ID / passport number), then tap **CREATE**.
{% endstep %}
{% endstepper %}

{% embed url="<https://app.arcade.software/share/1egvhGT77rtKNB0eeZF0?embed=true>" %}
Walkthrough: a returning visitor updating their stored profile at the kiosk.
{% endembed %}

{% hint style="info" %}
**Note:** a visitor who signs in without ever verifying a phone number (skipped during pre-registration or on site) gets only a **transactional record** on the visitor log. No directory profile is created.
{% 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 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://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/visitor-management/visitor-directory.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.