> ## 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.

# Incidents vs Emergencies in Rekkeh: Key Differences

> Learn the difference between incidents and emergencies in Rekkeh, how each is raised and managed, and what the practical implications are for your team.

Rekkeh separates security issues into two categories: incidents and emergencies. The distinction determines response speed, notification behavior, and escalation rules.

An **incident** is a report-and-review item. It can be raised by a guard in Gate Ops, a resident in the Member App, or an admin in the console. Incidents have categories such as unauthorized access attempt, property damage, or policy violation. They move through a lifecycle of reported, under review, resolved, or closed. Incidents are logged, assigned, and investigated without triggering an immediate facility-wide alert.

An **emergency** is a live alert that demands immediate response. When an emergency is raised, Rekkeh broadcasts notifications to designated responders, updates the live security dashboard, and starts an escalation timer based on your SLA. Emergencies have their own lifecycle: triggered, acknowledged, responding, contained, and resolved.

The practical difference is response time. An incident can wait for the next shift briefing; an emergency interrupts operations and requires immediate action. Panic and duress features in Gate Ops and the Member App can raise emergencies directly, while routine observations become incidents.

<CardGroup>
  <Card title="Understanding Incidents" icon="file-text" href="/security/understanding-incidents">
    Learn how incidents are categorized, reported, and resolved.
  </Card>

  <Card title="Understanding Emergencies" icon="alert-triangle" href="/security/understanding-emergencies">
    See how emergencies are triggered, escalated, and resolved.
  </Card>
</CardGroup>