> 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/invites/invite-log.md).

# The invite log

The invite log is the site's record of invited visitors. It lists every visitor invited to the site, whether the invite was created through the dashboard or the iCal bot, with who they are, who they are visiting, when they are expected, and whether they have pre-registered. A host who opens the log sees the invites they created. Open it from **Visitors → Invites** in the left panel. The page is headed **Visitor Invites - Manage and track visitor invitations**.

{% embed url="<https://app.arcade.software/share/XpxzLWp6gd1eY6xET91a?embed=true>" %}
Walkthrough: using the Visitor Invites log end to end.
{% endembed %}

## Columns

| Column           | What it shows                                                                    |
| ---------------- | -------------------------------------------------------------------------------- |
| **Photo**        | The visitor's photo, where one is registered or captured.                        |
| **Full name**    | The visitor's name and email.                                                    |
| **Host**         | The person the visitor has come to visit.                                        |
| **Site**         | The invited site.                                                                |
| **Due at**       | When the visitor is expected.                                                    |
| **Arrived at**   | When the visitor arrived, or the **Mark as arrived** action while they have not. |
| **Registration** | Pre-registration status, such as *Sent* or *Registered*.                         |

## Choose a date range

The log shows invites for a date range. Use the date-range selector at the top of the table to choose the period you want.

1. Click the date range (for example **Apr 20, 2026 to Apr 20, 2026**).
2. Pick a preset (**Today**, **Yesterday**, **Last 7 days**, **Last 30 days**, **Last 3 months**, **Year to date**, **Last year**) or select dates on the calendar.
3. Click **Apply**. The table reloads for the new range. Click **Reset** to clear your selection.

## Export the log

Export the rows currently in view.

1. Set the date range you want to export.
2. Click the export control at the top right of the table.
3. Choose **Download as CSV** or **Download as Excel**.

## Choose, sort, and pin columns

Tailor which columns appear and how the table is ordered.

* **Choose columns.** Open the **Columns** panel on the right edge of the table and tick or untick a column (for example **Full name**, **Host**, **Host Summary**, **Site**, **Due at**, **Arrived at**, **Registration**, **Check-in Values**, **Actions**). The table re-renders as you change the selection.
* **Sort and pin.** Open a column header's menu for **Sort Ascending**, **Sort Descending**, **Pin Column**, **Autosize This Column**, **Autosize All Columns**, **Group by Full name**, **Choose Columns**, and **Reset Columns**.

## Save a view

Save a column and filter configuration so you can return to it later.

{% stepper %}
{% step %}

### Open Saved Views

Open the **Saved Views** panel on the right edge of the table. It is headed **Saved Views - Save and restore view configurations** and lists any views you have saved.
{% endstep %}

{% step %}

### Save the current view

Click **Save Current View**, enter a name in the **Save View** dialog, and click **Save**. A *View saved successfully* message confirms it.
{% endstep %}

{% step %}

### Restore or reset

Select a saved view to restore it, or click **Reset to Default** to return to the default configuration.
{% endstep %}
{% endstepper %}

## Filter columns

Every column has a filter, reached from the filter icon in its header.

1. Click the filter icon on the column you want to narrow.
2. Set the filter (for example tick **Registered** or **Sent** on the **Registration** column).
3. The table updates to show only matching rows. The row count below the table reads, for example, *Rows: 4 of 6*.

To review or remove the filters you have applied, open the **Filters** panel on the right edge of the table. It lists each active filter, lets you remove one with its **x**, and offers **Add Filter**.

## Mark a guest as arrived

You can record an arrival from the log without a kiosk check-in.

1. In the visitor's row, click **Mark as arrived** in the **Arrived at** column.
2. In the confirmation dialog (*Are you sure you want to mark this invitee as arrived?*), click **Mark as arrived**. The **Arrived at** cell updates with the arrival time.

## View host details

Hover the **Host** to open the host's details (name, email, and phone where available) so you can make contact if needed.

{% hint style="info" %}
**Note:** *Registration* reflects pre-registration status, not whether the visitor has checked in for the visit.
{% 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/invites/invite-log.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.
