Settings

Settings is where the hotel's own configuration lives — details that rarely change day to day but shape how every other module behaves. It is normally restricted to admins.

1. Hotel Profile

Your hotel's name, logo, address, contact details and slogan — used on printed receipts, guest bills, and reports. Update this once during onboarding and revisit it only if your branding or contact details change.

2. Localization & Tax

• Set your default currency (e.g. XAF) and date/time format.
• Configure applicable taxes (VAT, tourism tax, etc.) and whether they're included in or added on top of displayed rates.
• Choose the default language for the dashboard interface (English/French) — individual users can still switch their own language from the header.

3. Front Desk Operations

Rules that govern how Reception behaves — default check-in and check-out times, whether early check-in or late check-out incurs a fee, and how rest bookings are priced by default. Changing these updates the defaults offered on new bookings; it does not alter bookings already made.

4. Cancellation Policy

Define how far in advance a booking can be cancelled for a full refund, any cancellation fee tiers closer to the arrival date, and no-show handling. This policy text can also be surfaced to guests at booking time if your setup includes a public booking form.

5. Account Reset

A dangerous, deliberate tool for wiping all operational data (bookings, transactions, business records, laundry orders, and more) while keeping your hotel profile and team accounts intact — meant for clearing out test data before going live, not for routine use.

• Review the list of data types that will be erased before confirming — it is shown explicitly so nothing is a surprise.
• This action cannot be undone. It is recommended you only use it once, right before real operations begin.

6. Notifications

Push notifications (for events like a laundry order becoming ready) are enabled per person from their own Profile page rather than from Settings — each staff member turns them on for the device/browser they actually use, with a single "Enable Notifications" button that requests permission from the browser.