> ## Documentation Index
> Fetch the complete documentation index at: https://docs.1club.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Access cards

> Manage the QR codes, access cards, and PINs that members use to check in at a reader or kiosk.

Access cards is the org-wide registry of credentials your members use to identify themselves: a QR code on their phone, a physical access card, or a PIN code. Each credential has a unique identifier, a status, and an optional contact assignment.

This page is named **Access cards** in the UI, even though it covers more than physical cards. The same page is reachable from the **Members** overflow menu and from a member's profile.

## Credential types

There are three credential types, matching the three identification methods configured under [Access control](/settings/access-control):

* **QR Code** - a code scannable at a reader or in the member portal.
* **Access Card** - a physical card with a number printed or encoded on it.
* **PIN Code** - a numeric code the member enters on a keypad.

The identifier value can be anything that uniquely identifies the credential within your org: a card serial, an NFC UID, a QR string, or a PIN. The hint on the enrollment form is "Enter the card number, NFC ID, or QR code value."

## Opening the page

Go to **Members > Access cards**, or open the overflow menu next to **Add Member** on the member list and pick **Access Cards**. The page shows every credential ever enrolled in the org.

The **Settings** button in the top right jumps to [Access control settings](/settings/access-control), where check-in mode and identification methods are configured.

## Grid columns

* **Assigned to** - the contact the credential belongs to, with avatar. A `+N more` chip appears when a credential is assigned to more than one contact (rare; allowed for household-style sharing). Unassigned credentials show an **Unassigned** chip.
* **Type** - QR Code, Access Card, or PIN Code.
* **Number** - the credential's identifier.
* **Status** - active, suspended, revoked, or expired.
* **Issued date** - when the credential was enrolled.
* **Expiry date** - optional expiry, or `-` if open-ended.

Click a row to inspect or act on the credential.

## Adding a credential

Click **Add Credential** in the top right:

1. Pick the type (QR Code, Access Card, PIN Code).
2. Enter the identifier.
3. Optionally pre-assign it to a contact. New credentials are added as non-primary; you can mark the credential primary later from its detail page (or from the contact's Access cards tab).

The credential is enrolled and appears in the grid immediately. You can also enroll a credential from a member's profile sidebar, which assigns it to that contact in one step.

## Assigning to a member

Unassigned credentials show an **Assign** action in the row menu. Pick a contact and choose whether this is their **primary** credential. A contact can have at most one primary credential; assigning a new primary automatically demotes the previous one.

From a member's profile, the **Assign** button in the credentials block lets you pick from the pool of unassigned credentials. The **Add** button enrolls a brand-new credential and assigns it in one step.

## Revoking and deleting

The row menu adapts to the credential's current state:

* **Unassigned and active** - can be assigned or **deleted** outright. Deletion is only allowed when there are no assignments on record.
* **Assigned and active** - can be **revoked**. The credential is marked revoked and rejected at the reader from then on; the row stays in the grid for audit.
* **Revoked** - can be **deleted** if you want to clear it from the grid. Otherwise it stays as a historical record.

Revoking by default revokes every active assignment of the credential. If a member loses their card, revoke the old credential and enroll a new one for them.

## Statuses

* **Active** - in use, accepted by readers.
* **Suspended** - temporarily disabled.
* **Revoked** - permanently disabled. The record is kept for the audit trail.
* **Expired** - past the optional `expiresAt` date.

## How credentials interact with check-in

How strict the door is, and what happens when a credential is presented, depends on your check-in mode. See [Check-in models](/reference/check-in-models) for the full matrix. Quick summary:

* **Strict** mode requires a credential to match an active booking or membership.
* **Flexible** mode allows walk-ins and anonymous check-ins.
* A scanned credential is matched to its primary contact, and the rest of the check-in flow proceeds as if you had selected that contact manually.

## Related

* [Access control](/settings/access-control) - check-in mode, identification methods, organization-level credential settings
* [Check-in models](/reference/check-in-models) - how credentials are honored at the reader
* [Member profile](/members/member-profiles) - per-contact credentials block
* [Attendance](/members/attendance) - the check-in log