📄️ Roles & Access Control
Nexa uses JWT bearer auth with role-based guards. Roles are scoped — an operator's authority is bounded by airport or tenant.
📄️ Background Jobs & Queues
Nexa runs every long-running step of a case (allocation, booking, notifications, payments, agent runs) on background workers. Customers do not operate queues or workers — Nexa runs them. This page describes how the platform behaves so integrators can reason about timing, retries, and failure modes from the API.
📄️ Idempotency
Nexa is designed to tolerate retries at every layer. This page lists the idempotency scopes and the keys that make each one safe.
📄️ Audit
Every state change in Nexa is recorded in an immutable audit log. No soft deletes, no mutations — only appends. Audit is the source of truth for compliance, finance, and incident postmortems.
📄️ Multi-tenant & Isolation
Nexa is a multi-tenant SaaS. Every airline (and, for groups and alliances, every member carrier) is provisioned with its own tenant — the isolation boundary for cases, passengers, policies, allocations, contracts, audit, and billing. This page describes the isolation guarantees customers can rely on.