> ## 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 Works: The Identity to Access Decision Chain

> Learn how Rekkeh orchestrates identity verification, access decisions, monitoring, and auditing into a single control chain for your facility.

Rekkeh models security as a continuous control chain rather than a single gate check. Every entry is the result of a sequence that produces a verifiable, accountable decision.

The chain has six links:

1. **Identity**: Rekkeh establishes who is requesting access using pre-registered visitor details, resident profiles, or kiosk-captured data.
2. **Verification**: The system checks whether the identity matches an active pass, a valid resident status, or an approved event invitation.
3. **Access Decision**: The Access Control Engine evaluates the pass type, expiration, flags, and site policies to produce an allow, deny, or escalate outcome.
4. **Monitoring**: Successful entries update live occupancy. Exits update the internal count. Security sees who is inside at any moment.
5. **Audit**: Every decision, including officer overrides and deny reasons, is written to tamper-resistant logs.
6. **Incident Response**: If an anomaly or emergency occurs, the same record chain feeds directly into incident and emergency workflows.

Rekkeh works as an authorization layer on top of your existing infrastructure: boom gates, turnstiles, RFID readers, and cameras. The five product surfaces (Admin, Kiosk, Access Control Engine, Gate Ops, and Member App) each own one part of the chain, producing a single source of truth for physical security.

<CardGroup>
  <Card title="What Is Rekkeh" icon="info" href="/understanding/what-is-rekkeh">
    Get the high-level overview of the platform and its purpose.
  </Card>

  <Card title="Access Control" icon="shield" href="/understanding/access-control">
    Dive deeper into passes, grants, and gate approvals.
  </Card>
</CardGroup>
