> 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/link-cards.md).

# Link an access card

Issue a physical access card to a visitor from the Guardian app so they can move through Gallagher-controlled doors during their visit. Link the card last, once the visitor has passed your other security checks.

**Before you start**

* Gallagher Command Centre integration must be set up for the site.
* Verify the visitor first (ID, induction, assets). Link the card only when they're cleared to enter.

{% stepper %}
{% step %}

### Open the visitor

In the **Visitor Log**, tap the visitor to open their **Visitor Profile**, then tap the **Link Access Card** tile.
{% endstep %}

{% step %}

### Enter the card number

Enter the card's RFID number. Kenai matches it to the existing Gallagher cardholder, or creates a new cardholder (in a ring-fenced division) if none is found.
{% endstep %}

{% step %}

### Confirm

Confirm to link the card. The tile changes to **Card Linked** and an **Access Card** chip appears on the visitor's profile and log entry. The visitor can now enter.
{% endstep %}
{% endstepper %}

{% embed url="<https://app.arcade.software/share/V1UAxbS45dcDbNH72ljl?embed=true>" %}
Walkthrough: linking an access card to a visitor in Guardian.
{% endembed %}

{% hint style="info" %}
**Note:** the card is automatically de-linked when the visitor signs out, so it no longer grants access once the visit ends.
{% endhint %}

{% hint style="warning" %}
**Warning:** a linked card grants the visitor its associated access. Issue cards only to visitors you've verified.
{% 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/link-cards.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.