Use named WordPress staff accounts and the smallest permissions needed for each operation. Viewing a booking, changing its lifecycle, recording money, exporting personal data and enabling an integration are separate authorities.
Start from the current role defaults
Receptionist receives dashboard and booking view/manage capabilities, not payment accounting, room inventory, channel or communication administration. Hotel Manager has broader hotel operations, including Contact/subscriber management, but communication settings and newsletter CSV export remain administrator-only by default.
Site-specific roles can differ. Inspect effective capabilities rather than granting Administrator because a screen is missing. WordPress Page publishing and native privacy permissions are not implied by the Hotel Manager label.
| Task | Current permission boundary |
|---|---|
| Booking operations | Dedicated booking capabilities |
| Ledger/refund operation | kimorapro_hb_manage_payments plus operation-specific checks |
| iCal/channel mutations | kimorapro_hb_manage_channels and entitled Pro owner |
| Communication configuration | kimorapro_hb_manage_communication_settings |
| Contact/subscriber management | Separate Contact and Newsletter management capabilities |
| Newsletter CSV export | kimorapro_hb_export_newsletter_subscribers |
| Native booking privacy | WordPress export/erase authority; erasure also requires delete_users |
| Demo Pack import | Administrator settings, upload and Page edit/publish capabilities |
Preserve action checks
State-changing controls require the relevant capability, valid nonce/input and the current owner-specific state checks. A nonce is not authorization. A booking code, signed guest link, subscriber token or iCal export URL is not staff authority.
Single-booking operations and bulk actions have their own target-bound request/claim checks. Refund preview/confirm also depends on original payment ownership, actor, amount, environment and freshness. Do not grant a capability to bypass a financial or entitlement rejection.
Review staff changes
Use synthetic data to test both allowed and denied requests after updates or role changes. Check that staff can complete their intended job while settings, exports, privacy tools and provider credentials remain appropriately restricted.
Remove or disable dormant access through the site’s normal account process and rotate compromised credentials with the owning service. Preserve audit records. A theme may render controls but cannot grant authorization or decide a Pro license.
For per-request attribution and hold review, see export and erase. Do not give every hotel operator WordPress privacy authority merely because they can view reservations.
