> ## Documentation Index
> Fetch the complete documentation index at: https://help.rekkeh.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Rekkeh verifies access at the gate

> Learn the five checks Rekkeh runs in order when someone presents a pass at the gate, plus supervisor override and who makes the final decision.

Every time someone presents a pass at your facility gate, Rekkeh runs a consistent sequence of checks before entry is granted. Understanding this sequence helps gate operators make informed decisions and helps admins set the right policies.

## The five checks in order

Rekkeh verifies access through five checks, run in this exact order:

### 1. Who are you?

The scanner reads the QR code or the operator enters the OTP. The system looks up the credential and identifies the bearer: resident, visitor, event guest, vendor, or contractor.

### 2. Why are you here?

The system retrieves the authorization record linked to the credential. It checks the pass type and the purpose of the visit: personal guest, event attendee, delivery, maintenance, school pickup, or other.

### 3. Are you authorized?

The system confirms that the pass exists, has not been revoked, and matches the facility and gate where it is being presented. A pass created for a different gate or facility is rejected.

### 4. Is authorization still valid?

The system checks the authorization window (start and end time) and, for rotating resident passes, the current QR code lifetime. Expired passes are rejected at this stage.

### 5. Should this person be allowed in?

The final check applies your organization's workflow rules and current conditions. This includes:

* Has the person already checked in? (single-entry rules)
* Is the facility under lockdown or emergency status?
* Is the bearer on a watchlist or blacklist?
* Does the pass require host approval that has not yet been given?

## Supervisor override

If the fifth check results in a deny or blacklist, a supervisor with the right role (Estate Manager, Platform Admin, or Security Officer) can override the decision. Override is audited with the supervisor's name and reason, and it requires an online connection. The Gate Ops app shows "OVERRIDE GRANTED" when successful.

<Warning>
  Do not use supervisor override for routine admits. Only use it for genuine emergencies, false positives, or exceptional cases.
</Warning>

## Who makes the final decision

The **Gate Ops operator** makes the final decision to grant or deny entry. The five checks provide the operator with a clear recommendation, but the operator can still choose to deny a valid pass or flag an issue for review. This human-in-the-loop design ensures that automated rules do not override common sense at the gate.
