Notifications

The in-app notification drawer and everything that can appear in it, who each alert reaches, how to turn on push for a device, and the emails Innvera sends.

Innvera tells staff what is happening in two ways. Notifications are the running feed behind the bell in the navbar: new bookings from channels, rooms taken off sale, work orders needing approval, sync errors, guest messages. They arrive live while the app is open and, if you turn it on, as push alerts on a device even when the tab is closed. Emails go to individual people at a handful of fixed moments — an account to verify, a password to reset, a staff invitation, a booking confirmation to a guest.

There is nothing to configure for either. Emails are sent from Innvera's own sender with fixed templates, and notifications are produced by the events themselves. Who receives a notification is decided by permissions, not by a setting: each alert names the permission its audience holds, and it is written only for the people at the property who hold it (plus the owner, who receives everything).

The notification drawer

Click the bell in the navbar; the badge shows the unread count, up to 99+. The drawer is titled Notifications with N unread or You're all caught up. beneath. Each entry has a coloured dot for its category, a title, a two-line body and a relative time; unread entries are bold on a tinted background. Housekeeping's urgent entries carry a red Urgent tag.

Click an entry to mark it read and jump to the screen it refers to — the reservation, the work order, the chat thread, the channel manager.
× dismisses one entry; Mark all read and Clear all act on the whole list.
An empty drawer reads No notifications — New reservations, channel sync issues and other alerts will appear here.
The list is filled from the server on load, kept current over a live connection while the app is open, and cached in the browser so it survives a reload.

Repeat deliveries are collapsed: a webhook that arrives twice, or a request that is retried, produces one entry, not two.

What can appear

Category	Title	Reaches	Opens
Reservation	New booking from <channel> / New reservation	`reservation: read`	The reservation
Reservation	Booking modified on <channel> / Reservation modified	`reservation: read`	The reservation
Reservation	Booking cancelled on <channel> / Reservation cancelled	`reservation: read`	The reservation
Reservation	Guest checked in, Guest checked out, Guest no-show	`reservation: read`	The reservation
Reservation	Unmapped room on booking, Unmapped rate on booking	`reservation: read`	Channel Manager settings
Reservation	Booking not acknowledged	`reservation: read`	Bookings
Reservation	Reservation request, Alteration request, Reservation accepted, Reservation declined	`reservation: read`	Bookings
Housekeeping	Housekeeping sheet published for <date>	`housekeeping: read_team`	Housekeeping
Housekeeping	Urgent task assigned — Room N (Urgent)	the attendant it was assigned to	Housekeeping, on that task
Housekeeping	Room N assigned to you, Room N removed from your tasks	the attendant concerned	Housekeeping, on that day
Housekeeping	Room N is ready	`reservation: read`	The arriving reservation
Housekeeping	Room N failed inspection	`housekeeping: assign` or `housekeeping: verify`	Housekeeping, on that task
Housekeeping	Room N: minibar charge not posted	`folio: post`	Housekeeping, on that task
Housekeeping	<Room> taken off sale (WO-…)	`maintenance: read` or `maintenance: close`	The work order
Housekeeping	Work order WO-… needs approval	`maintenance: approve` or `maintenance: close`	The work order
Housekeeping	Work order WO-… approved / rejected	the person who raised it	The work order
Channel	Sync error, Rate sync error, Sync warning	`channex: read`	Channel Manager settings
Channel	New channel, Channel activated, Channel deactivated, Channel disconnected, Listing disconnected	`channex: read`	Channel Manager settings
General	New message, New inquiry	`channex: read`	Chat
General	New review, Review updated	`channex: read`	Reviews

A reservation notification carries the detail in its body — the guest's name, the stay dates, the rooms and the OTA reference — so the feed is readable without opening anything. Guest checked out adds the outstanding balance when the folio is not clear.

Permissions decide the audience

An alert reaches the owner, every platform admin at the property, and every member whose roles grant any one of the permissions listed above. A storekeeper does not get reservation notifications; an attendant gets the rooms assigned to them and nothing about the ledger. If someone is missing an alert they should be seeing, the fix is their role, not a preference switch.

Turn on push for a device

Push uses the browser's own notification system, so it is enabled per device and per browser, not per account.

Open the switch

Either use the footer of the notification drawer — Get alerts even when this tab is closed. → Turn on — or go to your Profile, Notifications tab, Push Notifications card.

Allow the browser prompt

The browser asks whether this site may show notifications. Choose Allow. If you decline, push stays off and the footer reads Notifications are blocked in your browser settings for this site until you change it in the browser.

Confirm it is on

The drawer footer reads Push notifications are on for this device. Every notification you would receive in the drawer is now also delivered to this device. Turn off removes the device's subscription.

Two messages mean push is unavailable rather than off: This browser can't show push notifications. (the browser lacks the Push API — on iOS the app must be installed to the home screen first) and Push delivery isn't configured on this environment yet. (the server has no push keys; ask your Innvera contact).

Emails Innvera sends

Email	Subject	Sent when	To
Email verification	Verify your INNVERA email	An account is registered, or Resend is clicked on the verify-email screen	The new user
Password reset	Reset your INNVERA password	Send reset link on the Forgot password screen	The account's email
Staff invitation	You're invited to join <property> on INNVERA	An owner clicks Send invite under Users & Permission	The invitee
Booking confirmation	Your booking at <property> is confirmed — <code>	A guest completes a booking on the booking engine	The guest
Proforma invoice	Proforma invoice PI-00007 — <property>	Send on a proforma in Accounting	The company or guest it is addressed to

Reservation changes, check-in, housekeeping and channel events do not send email; they appear as notifications only. There is no screen for editing templates or the sender address, and none is needed — the settings rail is Property, Users & Permission, Accounting, Booking Engine, Channel Manager and Logs.

Per-user preferences

Your Profile's Notifications tab also has a Notification Preferences card — Choose which events trigger in-app notifications — with switches for New Reservation, Check-in Reminders, Check-out Reminders, Housekeeping Alerts, Billing Alerts and Channel Sync.

Coming soon

These switches are not connected yet: they do not filter the drawer, are not saved to your account, and reset when you reload. Check-in and check-out reminders and billing alerts are not produced by the server either. Until preferences are wired, what you receive is decided entirely by your permissions.

Tips

Use the bell, not your inbox, for operations. Booking, housekeeping and channel events never go to email.
Turn push on at the desk computer and on the supervisor's phone. A subscription is per device, so do it on each one that should ring.
Urgent means urgent. The red tag is only ever an urgent housekeeping task assignment; treat it as a page.
Cleared is not deleted everywhere. Clear all empties the drawer you are looking at; other devices keep their own list.

Roles and Permissions — the permissions that decide who is alerted
Messaging & Chat — where New message leads
Housekeeping — sheet, urgent tasks and room-ready alerts
Channel Manager — sync errors and channel lifecycle

On this page