> 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.md).

# Invites

An invite is how a host tells Kenai that a visitor is expected. It creates the visitor record, sends the visitor a branded email with a pre-registration link, and lets you track who's coming before they arrive. Only a host can create an invite, and only at a site where they're authorised to host.

There are three ways to create one: from the **Kenai dashboard**, from your **calendar** (the Kenai iCal bot), or through the **Kenai REST API**. They all produce the same result: an invite that the visitor can pre-register against and check in with on the day.

## Create an invite from the dashboard

If you have dashboard access, you can create an invite from several places: the **Invite Visitor** button on the home page, the **Invite a visitor** link in the **My expected visitors** panel, or the **New Invite** button on the **Invites** log (under **Visitors** in the left navigation). Each opens the same **New Invite** form, where you set the schedule, host and event, visitor details, and whether the visitor gets an email or SMS pre-registration link.

The dashboard supports single invites and group invites (**Invite and add another** adds more guests to the same event).

{% embed url="<https://app.arcade.software/share/16sgbB33R90ku8YVRvxn?embed=true>" %}
Walkthrough: creating a visitor invite from the Kenai dashboard.
{% endembed %}

{% content-ref url="/pages/YbPSgCRR4DXP11k0KSoI" %}
[Create an invite](/command-centre/visitor-management-powered-by-kenai/visitor-management/invites/inviting-visitors.md)
{% endcontent-ref %}

## Invite from your calendar (the iCal bot)

If you'd rather not open the dashboard, add the Kenai iCal bot as an attendee on a calendar event in Outlook, Google Calendar, or any iCal-compatible system, alongside your visitor. Kenai receives the event and emails you a **Set up Visitor Invites** link. You verify with a one-time pin, confirm the event details, and click **Create invites**. After the first setup, adding the bot to a meeting is all you need.

{% embed url="<https://app.arcade.software/share/IkTX0QU9cSC6EP2JWuTP?embed=true>" %}
Walkthrough: setting up visitor invites from a calendar event via the iCal bot.
{% endembed %}

## Invite through the API

You can also create invites programmatically through the Kenai REST API, driven from an upstream tool such as a booking or scheduling system. The visitor receives the same branded invitation and pre-registration flow as a dashboard or calendar invite.

## What the visitor receives

Every invite delivers a branded email to the visitor with host details, arrival instructions, a location map, and an embedded pre-registration link. Opening the link starts the pre-registration flow, where the visitor verifies their mobile number, confirms or builds their profile, and completes any required steps before arrival.

{% hint style="info" %}
**Note:** an invite is anchored to a single host and event. Track who's invited, due, and arrived on the **Invites** log.
{% 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.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.