# Administrator guide

## Initial handover

1. Confirm the installer is locked and `/install/` returns 404.
2. Sign in with the initial administrator, immediately change the temporary password, and verify the previous session is revoked.
3. Complete airline legal/trading details, codes, base currency, default timezone, bases, branding, tax settings, number sequences, alert thresholds, receipt rules, and password/session policy.
4. Remove demonstration/default accounts and revoke unused sessions, API tokens, and webhook endpoints.
5. Create named users; never share administrator accounts.

## Users and access

Assign the least-privilege default role and only required airline bases. Permission names use `module.action`. Hidden navigation is convenience only; controllers and services enforce permissions on the server.

For departures, deactivate the user and force logout. Review login and activity history. Reset passwords only after identity verification. Review privileged roles, active sessions, API clients, and integration credentials at least quarterly.

## Routine administration

- Review Administration → System health, pending migrations, storage, failed jobs, sessions, and backup status.
- Review audit logs for role, permission, settings, sequence, approval, maintenance release, payment, and session changes.
- Keep audit retention aligned to legal and operational policy.
- Test personal/business exports with a least-privilege account.
- Keep logs restricted to users with `administration.logs`.
- Treat cache clear and session revocation as audited administrative operations.

Changes to currency, timezone, approval thresholds, number sequences, or maintenance/document thresholds can affect future records. Record the business owner and effective time before changing them. Approved operational and financial history must not be overwritten.