Permissions and auditability are essential when operational AI can access guest, staff, financial and property records.
Illustrative capabilities, not a substitute for property-specific authorisation rules.
| Role | Typical information | Approval / action boundary |
|---|---|---|
| Frontline staff | Approved SOPs and assigned guest requests | Escalate costs and exceptions |
| Department head | Department operations, rosters and issues | Department limits and approvals |
| General manager | Property-wide performance and service | Approved property authority |
| Regional / brand | Authorised multi-property aggregates | Limited to assigned portfolio |
| Owner / asset manager | Approved commercial and asset views | No automatic access to guest/staff personal data |
Enforce permissions on the server, not only by hiding screens or instructing a language model.
Financial commitments, external services and consequential actions require explicit authority and logged review.
Keep provenance, policy versions and access records appropriate to the property's legal requirements.