> 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/setting-up-a-new-environment/configuration-and-integration/configure-the-sign-in-event.md).

# Configure the sign in event

Configuring the sign in integration event, section by section.

Work through the sections in order.

1. **Division and PDF group.** Pick from the extracted divisions, then the personal data field group holding the cardholder fields.
2. **Lookup fields.** Primary should be phone. Secondary is optional and usually email.
3. **Field mappings.** Update name, photo with an overwrite option, and custom mappings such as the Gallagher company PDF.
4. **Access granting groups.** From and until: at sign in, before end of day, minutes after sign in, or indefinite. Optionally extend an existing record.
5. **Cards and credentials.** Access pass card number, drawing on the [number range](/knowledge-hub/kenai-user-guide/setting-up-a-new-environment/the-kenai-connector/number-ranges.md), and Gallagher mobile credential.
6. **Error notifications.** Recipients for failures on this event specifically.
7. **Active.** Return to the top, set the event Active, save the draft, and publish.

{% hint style="warning" %}
Nothing fires until the event is set Active and the draft is published. The Active toggle often cannot be enabled until the other sections are filled in, so set it last.
{% endhint %}

## Related events

* **Sign out** reads back the groups granted at sign in or pre-registration and ends them.
* **Pre-registration** adds timing relative to the visit, and visit-scoped rollback when a meeting moves.


---

# 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/setting-up-a-new-environment/configuration-and-integration/configure-the-sign-in-event.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.