Notifications
Tune alert categories under Preferences — In-app notifications during setup steps 1–12, then triage the Dashboard bell and /notifications after steps 13–15 go live — Notification triage. Lockout catch-up: Getting Started — Lockout catch-up after password recovery. Workflow pairing: Modules — Setup sequence after go-live.
Start with Key Workflows — especially Payment overdue alerts (in-app) — then Interface Overview and Read status and list queries. Compare the Dashboard bell slide-over with the full /notifications module. Guide subsection map: Notifications guide subsection index (triage sections + Related subsections). Non-linear operator habits (Lockout catch-up, Pending manual receipt approval, Reject/revert mistaken receipts, Partly collected security deposit, Booking sidebar tab load failures, Confirmation alert triage, Finance debt receivables triage, Finance Income status drill-down, Cash flow forecast drill-down, Portfolio segmentation by tenant category) have matching Related subsections below. Full pairing matrix: Notifications section cross-reference · Modules — Module cross-reference.
The Notifications module is your central inbox for in-app alerts. It displays all notifications sent by the platform: new bookings, payment events, ticket updates, and other important events. You can search, filter, and mark notifications as read to stay on top of what matters.
Reply to WhatsApp rows via Inbox; compare with Dashboard bell slide-over before opening /notifications. When payment overdue Payments rows cluster on one tenant category, scope Bookings — Other filters tenant category or Finance — Tenant category filter before account-wide reminder or portal changes — see Glossary — Tenant category. Internal LLM token spend is not listed in this inbox — during Portfolio KPI review — Step 7 poll AI usage API (GET /ai-usage/summary; landlord_chat, utility_bill_extraction). Section-to-doc pairing: Notifications section cross-reference. Hub tab matrix: Modules — Module cross-reference.
User Roles and Access
| Role | Access |
|---|---|
| Property Manager | Full access — view, search, filter, and mark notifications as read |
| Admin | Full access |
| Viewer | Typically read-only; access depends on account configuration |
Prerequisites
- An active Vivin account
- Access to the management frontend (platform.vivin.app)
Open the Notifications module at platform.vivin.app/notifications. See Deep Links — Notifications for the bookmarkable route, how it compares to the Dashboard bell slide-over, and the Deep Links index for other management routes.
Key Workflows
Daily triage starts with Notification triage — use search and read-status pills here, then row-click into Bookings or Finance when alerts need follow-up. Full pairing matrix: Notifications section cross-reference.
Viewing Notifications
- Open the full Notifications module by navigating directly to
/notifications - Notifications are listed in reverse chronological order (newest first)
- Each notification shows:
- Summary — short title or subject
- Content — full message body
- Status — Unread or Read
- Date — when the notification was created
Filtering and Searching
Search and filter pills pair with Deep Links — Notifications (bookmark is always /notifications — pills are in-page only) and Notification triage — Step 5 when you clear unread after triage. Full pairing matrix: Notifications section cross-reference.
- Filter by status — Use the All, Unread, or Read buttons to filter the list
- Search — Type in the search box to find notifications by summary or content text (debounced; pause briefly after typing before expecting the list to update)
- Mark all as read — Click Mark all as read to clear the unread state for all notifications
With All selected, a search term narrows the list to rows whose summary or body matches (counts in the totals line update to match):
When nothing matches the active filter and search together, the list shows No notifications found for the selected filters. — switch pills or clear search before assuming data is missing:
Search results and empty-state captures refreshed 2026-06-17 03:10 UTC (VIVIN_DOCS_BASE_URL=http://localhost:5173 VIVIN_DOCS_RECORD_API=$VITE_API_BASE_URL npx tsx tools/capture-notifications-search-screenshots.ts).
Dashboard bell vs. full module
Bell Inbox sub-tab pairs with Inbox module; General payment rows pair with Handling a Late Payment — Step 1. Full pairing matrix: Notifications section cross-reference.
On desktop, the Dashboard (/) shows a bell in the page header (next to the title). Clicking it opens a Notifications slide-over from the right with General and Inbox sub-tabs (#1812): General holds payment, ticket, and booking alerts; Inbox holds inbound WhatsApp and email message pings (one notification per conversation, coalesced when new messages arrive). Each sub-tab has its own unread badge; Mark all as read clears only the active sub-tab. Inbox rows with a backend link navigate straight to the conversation (for example /inbox?contact=… or a booking Communication deep link) and mark the row read — other rows open Notification detail inside the panel. The slide-over scrolls with infinite load, Mark all as read, and footer totals. It does not include search or All / Unread / Read filters, and General rows without a link do not jump to Bookings, Tenants, or Listings from the bell alone.
Inbox sub-tab row labels (#1812) — summaries are conversation-scoped, not one row per message:
| Channel | Summary (English UI) | Body preview |
|---|---|---|
New WhatsApp message from {tenant name} when the phone matches a tenant; otherwise New WhatsApp message from +{digits} | Last inbound message text (or New WhatsApp message) | |
New email from {sender} — display name when present, otherwise the From address | Gmail snippet or subject |
A new inbound message on an existing thread bumps that row to the top and marks it unread again instead of inserting a duplicate. The full /notifications page lists Inbox and General rows together (no category pill) — use the bell Inbox sub-tab when you only want message triage. See Inbox — Dashboard bell.
When the account tenant chatbot is not enabled (isTenantChatBotEnabled), the Inbox sub-tab is greyed out and cannot be selected — hover shows Activate the Chatbot to get tenant messages right here. General remains fully usable. The same flag gates Tools → Inbox and Bookings → Communication; see Inbox — Chatbot gating and ChatBot settings — Inbox and Dashboard bell gating.
The bell is not added to other modules’ page headers in the current layout, and it is not shown on narrow (mobile) viewports. The left sidebar lists Inbox under Tools (/inbox) on desktop when your role includes Bookings access — see Inbox module.
Bell Inbox sub-tab capture refreshed 2026-06-17 14:15 UTC (npx tsx tools/capture-notifications-dashboard-bell-inbox-tab-screenshot.ts — develop NotificationsPanel #1812).
Bell Inbox chatbot-disabled capture refreshed 2026-06-17 18:05 UTC (npx tsx tools/capture-notifications-dashboard-bell-inbox-chatbot-disabled-screenshot.ts).
For search, read-status filters, full General history, and one-click entity navigation from payment/ticket rows, open the Notifications module directly — for example platform.vivin.app/notifications or your bookmarked /notifications URL. See Deep Links > Notifications.
Payment received alerts (email + in-app)
Payment-received rows pair with Settings — Preferences masters and Finance — Pending manual payments when receipts stay pending after row-click. Full pairing matrix: Notifications section cross-reference.
When a tenant payment is received, opted-in operators can get both a mailbox email and an in-app row in this history (Dashboard bell and /notifications). Delivery requires both layers on for each recipient:
- Account — Preferences → Notifications & Emails: Receive payment notifications.
- You — Personal Settings (
/settings/personal): Payment notification emails — the same toggle controls your email and whether you see in-app payment-received rows.
Row shape: summary like Payment received from tenant …; body includes amount, listing, and property. When bookingId is set, clicking the row on /notifications opens the booking sidebar (see Open the related booking, tenant, or listing).
Audience scoping: in-app rows are created with a per-user audience list — only property managers who opted in on Payment notification emails see them. Teammates who did not opt in will not see those rows (and their unread counts differ). Legacy rows with no audience list remain visible to every signed-in user on the account.
See Glossary — Payment notification (operator), Notification triage — Step 4, and Handling a Late Payment — Step 4b when the receipt still shows pending after row-click navigation.
Payment overdue alerts (in-app)
Overdue Payments rows pair with Finance — Tenant category filter and Bookings — Other filters tenant category when alerts cluster on one segment — see Glossary — Tenant category. Full pairing matrix: Notifications section cross-reference.
When a scheduled charge is overdue or a booking balance triggers an operator alert, in-app rows under the Payments category can appear on /notifications and the Dashboard bell (subject to the same In-app notification preferences masters and personal opt-outs as payment-received rows).
Row-click navigation: when bookingId (or tenantId / listingId / propertyId) is set, clicking the row on /notifications opens the related entity — then continue collections on Handling a Late Payment — Step 1. When overdue rows cluster on one tenant category, add Finance — Tenant category filter or Bookings — Other filters tenant category before you chase every alert individually — see Glossary — Tenant category. See Notification triage — Step 4 and Glossary — Payment notification (operator).
In-app notification preferences
Operator in-app rows on the Dashboard bell and /notifications are grouped into four categories. Each category is controlled by two layers:
- Account — Preferences → In-app notifications: master switches (Payments, Service requests, Scheduled bookings, Inbox messages). When a master is Off, no user sees that category in-app.
- You — Personal Settings → Your in-app notifications: per-user opt-out toggles (default On). Turning a toggle Off hides that category for your session only.
| Category | Example row summaries | Extra gate for Payments only |
|---|---|---|
| Payments | Payment received from tenant … | Also requires account Receive payment notifications and your Payment notification emails audience opt-in — see Payment received alerts |
| Service requests | Portal service order / cancellation summaries | Service-order emails use Service subscription emails on Personal Settings (separate from in-app) |
| Scheduled bookings | Scheduled import or booking job success / failure | — |
| Inbox messages | New WhatsApp message from …, New email from …, chatbot handoff pings | Dashboard bell Inbox sub-tab when Chatbot is enabled |
Legacy rows with no eventType remain visible unless filtered by search or read-status pills. Preference lookup errors fail open (rows stay visible) so a transient API issue does not blank the module.
Pending manual in-payments (approval queue)
Pending-manual rows pair with FAQ — Pending manual in-payment on /notifications, FAQ — Manual receipt still pending, Glossary — Pending manual in-payment (Finance), Common Workflows — Pending manual receipt approval, and Notification triage — Step 4. Full pairing matrix: Notifications section cross-reference.
When someone records a manual in-payment on Finance → Add Payment or a booking Transactions tab, the receipt often stays pending until a user with Approve payments confirms it. Until approval, Total Debt, Contract Values, and Payment Plan pills may still show the old balance even though the bank deposit arrived — and a Pending manual in-payment row may remain on /notifications until ledger approval clears.
Triage from Transactions — Finance → Overview shows a Manual Payments KPI for the selected month (€ total + transaction count for all manual rails, including pending). Clicking the card opens the month drill-down of all manual rails — it does not isolate the approval queue. Open Finance → Transactions (Pending pill, row icons, or Approve selected / Reject selected bulk bar) to approve. Ledger Reject is bulk-only — there is no per-row reject icon on Finance. Reject and Revert modals warn about credit notes when Finance may already have invoiced the charge. Hub matrix: Common Workflows — Pending manual receipt approval.
After you approve or reject from the booking sidebar or ledger, return to /notifications and Mark as read on any related payment alerts when balances look correct. Full operator rhythm: Notification triage — Step 4, Notification triage — Step 5, FAQ — Manual receipt still pending, FAQ — Pending manual in-payment on /notifications, Finance — Pending manual payments, Bookings > Transactions — Row actions, Payment Allocation — Pending manual approval (month-end habit), and Payment Allocation — Correcting mistaken receipts.
Marking Individual Notifications as Read
For unread notifications, click Mark as read to update the status. This helps you track which items you have already reviewed.
Open the related booking, tenant, or listing
Row-click navigation pairs with Notification triage — Step 4 and Glossary — Notification row navigation — bell General rows without link stay in-panel only. Full pairing matrix: Notifications section cross-reference.
On the full Notifications page (/notifications), clicking a row does more than update read status when the platform attached a navigation target:
- If the row is still Unread, it is marked read in the background (no success toast on row click alone — same as before).
- The app then navigates to the related workspace when possible, using the first match in this order:
link— backend-provided deep link (when present)bookingId→/bookings/list/:bookingIdtenantId→/tenants/:tenantIdlistingId→/listings/unit/:listingIdpropertyId→/listings/property/:propertyId
If none of those fields are set, the row is marked read when applicable but you stay on the inbox — use Mark as read when you only want to clear unread without leaving the page.
This behaviour applies to the full module only. On desktop Dashboard, the header bell slide-over opens Notification detail inside the panel for General rows without a deep link, or navigates directly when the row carries a link (Inbox message notifications jump to /inbox or booking Communication). Use /notifications when you want search, filters, and one-click triage into Bookings, Tenants, or Listings from General payment and ticket rows.
Row-click triage captures refreshed 2026-06-20 15:08 UTC (VIVIN_DOCS_BASE_URL=http://localhost:5173 VIVIN_DOCS_RECORD_API=$VITE_API_BASE_URL npx tsx tools/capture-notifications-row-navigation.ts — publication-clean bookingId row, not default Inbox WhatsApp row). Walkthrough MP4 added 2026-06-20 15:08 UTC (tools/record-notifications-row-navigation-mp4.ts).
Hub matrix: Common Workflows — Notification row-click navigation. See FAQ — Notification row-click navigation, Glossary — Notification row navigation, Notification triage — Step 4, Deep Links — Notifications, Bookings, Tenants, Listings, Portfolio KPI review — Dashboard Total Debt subtitle, and Deep Links — Broken entity deep links when a target id no longer exists.
Notification Types
Notifications can relate to:
| Category | Examples |
|---|---|
| Bookings | New booking created, booking confirmed, cancellation |
| Payments | Payment received, payment overdue, deposit returned |
| Tickets | New ticket created, ticket assigned, ticket resolved |
| System | Account updates, integration alerts |
On desktop Dashboard, the header bell shows an unread badge when applicable and opens the slide-over for recent notifications. The full Notifications page at /notifications is where you search, filter by read status, and review complete history.
Interface Overview
Toolbar controls pair with Settings — Interface Language — Your in-app notifications opt-outs and Glossary — Notification read actions for Mark all as read toasts. Full pairing matrix: Notifications section cross-reference.
The full Notifications page is a single column inside the main content area (there is no extra sub-navigation beyond the filter pills).
Toolbar row
- Search — Text field above the list; matches against notification summary and body (search is debounced, so pause briefly after typing before expecting results).
- Mark all as read — Enabled when there is at least one unread item; disabled when every item is already read or while the request is in progress. On success, a toast confirms All notifications marked as read.; on failure, an error toast asks you to retry and unread badges stay unchanged (see Glossary — Notification read actions).
List load and read actions
Load failures pair with FAQ & Troubleshooting — distinct from filter-empty states when the fetch succeeded but nothing matches. Full pairing matrix: Notifications section cross-reference.
Initial load failure — If the first notifications request fails, the page shows Failed to load notifications. in red inside the main panel with a Try again control (not the empty-state copy). This is distinct from No notifications found for the selected filters. when the fetch succeeded but nothing matches.
Load-failure capture refreshed 2026-06-16 22:07 UTC (VIVIN_DOCS_BASE_URL=http://localhost:5173 VIVIN_DOCS_RECORD_API=$VITE_API_BASE_URL npx tsx tools/capture-notifications-module-load-failure.ts — simulates GET /notifications failure after a successful first load by switching to the Unread filter).
Per-row Mark as read — The explicit Mark as read control shows success or error toasts. Row click still marks unread items in the background without a success toast when navigation or in-panel detail is the primary action (Dashboard bell detail view behaves the same).
Mark all as read — Available on the full page and in the Dashboard bell slide-over. While the request runs, the control is disabled. Failures surface as a toast; retry after connectivity improves.
Filters and counts
- All / Unread / Read — Pill-style toggles; the active pill uses the primary teal styling. The visible words on each pill follow your Interface language; behaviour is the same in every locale.
- Totals line — Shows how many notifications match the current query and how many are still unread (wording follows your interface language).
Why counts differ between teammates: booking, ticket, and most system rows are account-wide — every signed-in user with access sees the same history. Payment received rows are scoped to opted-in property managers only (see Payment received alerts above). If your bell badge or unread total does not match a colleague’s, check whether you both enabled Payment notification emails on /settings/personal and whether the account Receive payment notifications switch is on.
Notification rows
Each row is one notification. Unread items show an Unread badge; read items show Read. The body text preserves line breaks where the platform stored them. Mark as read appears on unread rows when you want to clear unread without navigating away.
On this full page, clicking the row marks unread items read (when applicable) and, when the notification includes a target, opens the related booking, tenant, or listing — see Open the related booking, tenant, or listing. Use Mark as read when you only need to update status and stay in the inbox.
The Dashboard header bell slide-over is a lighter variant of the same inbox (no read-status pills inside the panel), with General and Inbox sub-tabs when the WhatsApp global inbox release is active — see Inbox module. General rows without a link open in-panel detail only; use /notifications when you want search, filters, and one-click triage into Bookings, Tenants, or Listings from payment and ticket alerts.
Dashboard bell slide-over loading (infinite scroll)
The compact panel is also server-paged. The first open loads a batch of rows (enough for a quick scan); when you scroll near the bottom of the panel’s list, the app fetches the next batch automatically. While the next batch loads, skeleton rows appear at the bottom of the slide-over list (same row shape as the full /notifications page, but inside the narrower panel). The panel does not show an End of list line — keep scrolling until the footer total count matches what you expect, or open /notifications when you need filters, search, and the explicit end-of-history marker.
Click a row to open Notification detail inside the panel (summary, body, created time). The header title becomes Notification Detail, the General / Inbox sub-tabs hide, and the back arrow (←) beside the title returns you to the list for the same sub-tab. Opening a row that is still Unread marks it read (without a success toast on row click alone). The bell panel does not route to Bookings, Tenants, or Listings — open /notifications for that workflow.
Bell Notification detail capture refreshed 2026-06-18 17:00 UTC (VIVIN_DOCS_BASE_URL=http://localhost:5173 VIVIN_DOCS_RECORD_API=$VITE_API_BASE_URL npx tsx tools/capture-notifications-bell-detail.ts — panel-scoped clone check).
Read status and list queries
Read-status pills pair with teammate payment-received audience scoping — check Personal Settings — Payment notification emails when bell badges differ between colleagues. Full pairing matrix: Notifications section cross-reference.
The All, Unread, and Read pills are mutually exclusive: only one read-status filter applies at a time, together with whatever you typed in search (after the short debounce). Changing the pill replaces the underlying list query and starts again from the first page of results, so you always see one coherent slice — every matching notification, only unread rows, or only rows already marked read.
The totals line under the toolbar reflects that same combination (filter + search), not a second hidden query. If you pick Read and see no rows, either nothing read matches your search yet or your history is still entirely unread; switch to All or clear search to confirm what exists before assuming data is missing.
History loading (infinite scroll)
Infinite scroll pairs with Dashboard bell skeleton loading — use /notifications when you need End of list, search, and read-status filters together. Full pairing matrix: Notifications section cross-reference.
The notification list is server-paged like other large directories. The first request loads a batch of rows; as you scroll near the bottom of the scrollable list (inside the bordered panel), the app fetches the next batch automatically. While the next batch loads, compact skeleton rows appear at the bottom of that panel:
When every notification matching the current filter + search is loaded, an End of list line appears below the list. Changing the All / Unread / Read pill or the search box clears the list and starts again from the first batch.
End of list capture refreshed 2026-06-22 03:25 UTC (VIVIN_DOCS_BASE_URL=http://localhost:5173 VIVIN_DOCS_RECORD_API=$VITE_API_BASE_URL npx tsx tools/capture-notifications-module-end-of-list-screenshot.ts — mocks a 25-row paginated history so the marker appears without scrolling 3600+ live rows).
Screenshots
Full Notifications page (/notifications) — All filter, search, Mark all as read, and totals line:
Unread filter narrows the list to items still marked unread (counts update in the totals line):
Read filter shows only notifications already marked read (same search and Mark all as read row; the Read pill uses the primary teal active styling when selected). When nothing matches, you see the standard empty state (“no notifications for the selected filters”) — that is still a valid Read filter outcome.
When no notifications match the current filter (for example you have no read items yet, or search text matches nothing), the list area shows the standard empty state: No notifications found for the selected filters. That is expected behaviour — switch back to All or Unread, clear the search box, or wait for new events. See the search empty-state capture above.
The URL is always /notifications. All, Unread, and Read are in-page only; a bookmark cannot open the module already filtered to Read. See Deep Links — Notifications.
Dashboard (desktop) — bell in the page header opens the slide-over (scroll the list to load more history; footer shows total and unread):
Bell General slide-over list capture refreshed 2026-06-22 01:20 UTC (VIVIN_DOCS_BASE_URL=http://localhost:5173 VIVIN_DOCS_RECORD_API=$VITE_API_BASE_URL npx tsx tools/capture-notifications-dashboard-bell-slideover-open-screenshot.ts).
Notifications guide subsection index
This index pairs Notifications triage sections with Related subsections — use it when bell General rows disagree with full /notifications search or read-status pills. Full pairing matrix: Notifications section cross-reference.
Notifications section cross-reference
Use this table when one Notifications section or control naturally leads into another module, workflow, or concept — each row links to the docs you should read before or after acting in that section.
Related
Related below links this module to settings, concepts, workflows, and escalation paths. Pair Documentation map & escalation with Modules hub — Documentation map & escalation; pair Upstream & downstream workflows with Common Workflows — Workflow cross-reference. Topic-to-section pairing in sections above: Notifications guide subsection index · Notifications section cross-reference. Full hub matrix: Module cross-reference · Modules hub subsection index.
Documentation map & escalation
Documentation-map bullets pair with Introduction — Section cross-reference and FAQ — Section cross-reference. Hub parity: Modules hub — Documentation map & escalation. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Modules hub — Hub pairing matrix across operator workspaces
- Deep Links — Notifications — Bookmarkable
/notificationsURL and Dashboard bell behaviour - Getting Started > Interface layout — Dashboard bell and full
/notificationsroute - Using in-app support — Vivin platform support tickets (distinct from product notification rows)
- Notifications section cross-reference — Section-to-module pairing table on this page
Upstream & downstream workflows
Workflow bullets pair with Common Workflows — Workflow cross-reference. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Notification triage (workflow) (section cross-reference; Deeper workflow reads; hub) — Step-by-step guide after busy booking or payment days
- Portfolio KPI review (section cross-reference; Deeper workflow reads; hub) — Month-end pass that should clear stale unread rows before reconciling Dashboard and Analytics KPIs
- Handling a Late Payment (section cross-reference; Deeper workflow reads; hub) — Collections workflow when payment alerts need Finance → Transactions follow-up
- Manual block hygiene (section cross-reference; Deeper workflow reads; hub) — Availability alerts that clear after Audit removes stale manual blocks on Sales
- Cancelling a Booking (section cross-reference; Deeper workflow reads; hub) — Clear booking alerts after early termination is recorded
- Managing a Check-out & Deposit Refund (section cross-reference; Deeper workflow reads; hub) — Clear payment alerts after departure-week settlement (Step 6)
Deeper workflow reads
Workflow reads pair with Common Workflows hub subsection index and Workflow cross-reference. Each workflow sub-guide reciprocates with [Deeper workflow reads](../modules/notifications/index.md#deeper-workflow-reads) anchors on Module documentation hubs bullets — hub parity: Modules hub — Deeper workflow reads. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Notification triage (workflow) — Step-by-step guide after busy booking or payment days (section cross-reference; Deeper API reads; hub)
- Portfolio KPI review — Month-end pass that should clear stale unread rows before reconciling Dashboard and Analytics KPIs (section cross-reference; Deeper API reads; hub)
- Handling a Late Payment — Collections workflow when payment alerts need Finance → Transactions follow-up (section cross-reference; Deeper API reads; hub)
- Manual block hygiene — Availability alerts that clear after Audit removes stale manual blocks on Sales (section cross-reference; Deeper API reads; hub)
- Cancelling a Booking — Clear booking alerts after early termination is recorded (section cross-reference; Deeper API reads; hub)
- Managing a Check-out & Deposit Refund — Clear payment alerts after departure-week settlement (section cross-reference; Deeper API reads; hub)
Settings that shape Notifications
Settings bullets pair with Account Settings — Tab cross-reference. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Settings > Preferences — In-app notifications — Account-wide category master switches before personal opt-out
- Settings > Interface Language — Your in-app notifications — Per-user category opt-outs
- Settings > Preferences — Account-level Receive payment notifications switch before personal opt-in
- Settings > Interface Language — Per-user email toggles that shape which payment rows appear here
- Settings > Chatbot — WhatsApp bot alerts that appear under bell Inbox rows
- Settings > Tenant categories — Segment definitions when Payments alerts cluster on one cohort — pair with Bookings — Other filters tenant category and Finance — Tenant category filter
- Settings > Emails — Communication Rules that generate some payment and lifecycle alerts surfaced here
Deeper concept reads
Concept reads pair with Concepts hub subsection index and Concept cross-reference. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Automation & AI — Communication Rules and chatbot channels that generate some rows surfaced here (section cross-reference; hub)
- Integrations (concept) — Channel import alerts that sometimes precede payment notifications (section cross-reference; hub)
- Booking Lifecycle — Computed Upcoming → Ongoing → Ended / Canceled status model, list filters, and Timeline (section cross-reference; hub)
- Services Marketplace — Service requests alerts after portal orders need operator approval on Settings → Services (section cross-reference; hub)
- Landlord MCP — External automation that may triage the same alert categories before row-click navigation (section cross-reference; hub)
Operator modules (pairing surfaces)
Module hub bullets pair with Modules — Module cross-reference. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Bookings — Booking lifecycle and events (row-click navigation opens the detail sidebar)
- Bookings — Other filters tenant category — Portfolio segment filter when Payments alerts involve mixed tenant profiles
- Finance — Payment events
- Finance — Tenant category filter — In Debt triage by segment before account-wide reminder changes after alert triage
- Inbox module — Inbox sub-tab rows that deep-link into WhatsApp threads
- Operations — Ticket management
- Tenants module — Profile sidebar when tenant-scoped alerts carry
tenantId - Tenants — Tenant category filter — Profile-count cross-check before changing Communication Rules account-wide after payment alert triage
- Sales module — Availability context when channel sync disagrees with operator expectations
- Audit — Discounts tab — Cross-portfolio discount rows when payment alerts follow mid-stay repricing
- AI Chat module — Portfolio Q&A when alert volume suggests a cross-booking question before row-click navigation
Lockout catch-up after password recovery
Operational backlog after sign-in recovery pairs with Resetting a Management User Password — Step 3. Hub parity: Common Workflows — Lockout catch-up after password recovery. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Lockout catch-up after password recovery — Hub matrix when sign-in was restored and
/notificationsor bell backlog accumulated during lockout - Getting Started — Lockout catch-up after password recovery — Canonical operational backlog mesh
- Notification triage — Step 5 Mark all as read only after Step 4 row-click clears actionable rows
- Dashboard — Notifications bell — Slide-over quick triage before full
/notificationsmodule - Resetting a Management User Password — Step 3 — Recover access when lockout blocked alert triage
Pending manual receipt approval
Receipt approval pairs with Finance — Pending manual payments and Bookings — Transactions tab. Hub parity: Common Workflows — Pending manual receipt approval. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
-
Common Workflows — Pending manual receipt approval — Hub matrix when Pending manual in-payment rows persist on
/notificationsuntil Approve payments on Finance or Bookings Transactions -
Payment overdue alerts (in-app) — Operator Payments category rows; distinguish overdue charges from pending recorded transfers
-
Finance — Pending manual payments — Amber Pending chip and bulk Approve selected
-
FAQ — Pending manual in-payment on
/notifications— Why alert rows may remain until approval clears -
FAQ — Uncovered Debt KPI — Finance Total Debt minus deposit offsets; pair with Debt Aging and In debt drill-down
-
FAQ — Dashboard Total Debt subtitle — Post-login Total Debt card headline vs >15 days subtitle; ongoing bookings only
-
Glossary — Pending manual in-payment (Finance) — Definition and row-click pairing
-
FAQ — Pending manual receipt approval hub — Symptom table for Approve payments / amber Pending
Reject/revert mistaken receipts
Receipt cleanup pairs with Finance — Row actions on in-payment rows and Bookings — Row actions on in-payment rows. Hub parity: Common Workflows — Reject/revert mistaken receipts. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
-
Common Workflows — Reject/revert mistaken receipts — Hub matrix when payment alerts were triggered by duplicate receipts that need Reject / Revert after Approve
-
Notification triage — Step 4 — Row-click into Finance → Transactions or booking Transactions before reject/revert
-
Finance — Row actions on in-payment rows — Bulk Reject selected after alert triage
-
Payment Allocation — Correcting mistaken receipts — Two-layer model and credit note follow-up
-
Reject/revert mistaken receipts — Clear stale Payments category rows after ledger cleanup
-
FAQ — Reject/revert mistaken receipts hub — Symptom table for Reject / Revert / Issue credit notes
Check-out ledger cleanup before refund
Duplicate-transfer cleanup pairs with Reject/revert mistaken receipts and Managing a Check-out. Hub parity: Common Workflows — Check-out ledger cleanup before refund. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
-
Common Workflows — Check-out ledger cleanup before refund — Hub matrix when duplicate Pending manual in-payment alerts surface during departure week
-
Reject/revert mistaken receipts — Reject / Revert duplicate before Ready To Refund
-
Managing a Check-out — Step 6 — Canonical departure-week duplicate cleanup before refund
-
Common Workflows — Check-out collections before refund — Real arrears contrast (tenant did not pay)
-
Notification triage — Check-out ledger cleanup before refund — Row-click → Reject selected before Approve both
-
Payment overdue alerts in-app — Confirm duplicate vs real arrears before collections
-
FAQ — Check-out ledger cleanup before refund hub — Symptom table for phantom In Debt / Ready To Refund blocked when tenant paid once
Utility overage collections
payment overdue alerts after monthly bill cycles often cite utility overage lines — row-click to Payment Plan before collections. Hub parity: Common Workflows — Utility overage collections. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
-
Common Workflows — Utility overage collections — Hub matrix when payment overdue alerts surface utility overage In Debt after bill posting
-
Payment overdue alerts in-app — Overage alert before Handling a Late Payment — Step 1
-
Notification triage — Utility overage collections — Row-click → Step 4 before mark-read
-
Entering Monthly Utility Bills — Step 4 — Confirm overage line posted before outreach
-
Pending manual receipt approval — Overage Step 4b Pending mesh
-
FAQ — Utility overage collections hub — Symptom table for unpaid utility overage on Payment Plan after bill posting
Cancellation collections before void
Pre-cancel payment overdue alerts pair with Notification triage and Cancelling a Booking. Hub parity: Common Workflows — Cancellation collections before void. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
-
Common Workflows — Cancellation collections before void — Hub matrix when payment overdue alerts surface pre-cancel arrears before Cancel booking
-
Notification triage — Cancellation collections before void — Row-click → Step 2 before void
-
Payment overdue alerts in-app — Pre-cancel alert before policy void
-
Cancelling a Booking — Step 2 — Settle after row-click navigation
-
Handling a Late Payment — Steps 1–4 — Collections when arrears are real
-
Common Workflows — Check-out collections before refund — Departure-week alert contrast
-
FAQ — Cancellation collections before void hub — Symptom table for In Debt blocking Cancel booking until Payment Plan settles
Check-out collections before refund
Departure-week payment overdue alerts pair with Notification triage and Managing a Check-out. Hub parity: Common Workflows — Check-out collections before refund. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
-
Common Workflows — Check-out collections before refund — Hub matrix when payment overdue alerts block Ready To Refund during departure week
-
Notification triage — Check-out collections before refund — Row-click → Step 6 before refund
-
Payment overdue alerts in-app — Departure-week alert before refund queue
-
Managing a Check-out — Step 6 — Settlement after row-click navigation
-
Handling a Late Payment — Steps 1–4 — Collections when arrears are real
-
Common Workflows — Check-out ledger cleanup before refund — Duplicate Pending manual in-payment contrast
-
Common Workflows — Cancellation collections before void — Pre-cancel alert contrast
-
FAQ — Check-out collections before refund hub — Symptom table for rent/fee In Debt blocking Ready To Refund before deposit release
Handling a Late Payment collections
payment overdue alert batches on /notifications pair with Payment alert to receivables triage before Handling a Late Payment Steps 1–6. Hub parity: Common Workflows — Handling a Late Payment collections hub. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Handling a Late Payment collections hub — Hub matrix when payment overdue row-click needs collections Steps 1–6 (
notifications-row-navigate-to-booking-detail.png,notifications-row-navigation-flow.mp4,finance-overview-income-chart-debt-aging.png) - Payment overdue alerts in-app — Ongoing/Ended row-click entry
- Notification row-click navigation — Row-click before Step 1
- Payment alert to receivables triage — Alert → receivables surfaces before collections
- Finance debt receivables triage — Portfolio Debt Aging when alert batch needs rank
- Handling a Late Payment — Steps 1–3 — Collections after row-click confirm
- Pending manual receipt approval — Pending manual in-payment before Debt Aging sign-off
- Notification triage — Step 4 — Upstream alert path
- FAQ — Handling a Late Payment collections hub — Symptom table for triage surface → collections step pairing
Check-out vs cancellation
Departure-week vs pre-cancel alerts on /notifications need lifecycle context before you open Managing a Check-out or Cancelling a Booking. Hub parity: Common Workflows — Check-out vs cancellation. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Check-out vs cancellation — Hub matrix: route alerts to Ended vs Canceled workflows (
notifications-row-navigate-to-booking-detail.png,bookings-list-canceled-tab.png) - Payment overdue alerts in-app — Row-click → confirm booking status before exit routing
- Notification row-click navigation — Open booking before Cancel booking vs check-out steps
- Managing a Check-out — Step 6 — Departure-week settlement on Ended path
- Cancelling a Booking — Step 2 — Pre-cancel settlement on Canceled path
- Common Workflows — Check-out collections before refund — Departure-week arrears contrast
- Common Workflows — Cancellation collections before void — Pre-cancel void contrast
- FAQ — Check-out vs cancellation — Symptom table for lifecycle exit routing
Deposit missing on Finance Deposits
Deposit-related /notifications row-click usually lands on Bookings first — clear Finance → Deposits toolbar date range when the portfolio row is filtered out after you verify booking Deposit tab data. Hub parity: Common Workflows — Deposit missing on Finance Deposits. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Deposit missing on Finance Deposits — Hub matrix (
notifications-row-navigate-to-booking-detail.png,finance-deposits-date-range-clear-flow.mp4) - Notification triage — Deposit missing on Finance Deposits — Row-click deposit alerts when Finance row hidden (Step 4)
- Payment overdue alerts in-app — Distinguish rent arrears from deposit shortfall
- Bookings — Deposit tab — Per-booking deposit after row-click
- Finance — Deposits tab — Portfolio row after Clear date range selection
- FAQ — Deposit missing on Finance Deposits — Symptom table for toolbar date range triage
Notification row-click navigation
Row-click on /notifications pairs with Notification triage — Step 4 before bulk Mark all as read — hub parity: Common Workflows — Notification row-click navigation. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Notification row-click navigation — Hub matrix (
notifications-module-row-click-target.png,notifications-row-navigate-to-booking-detail.png,notifications-row-navigation-flow.mp4) - Dashboard — Notification row-click navigation — Post-login bell backlog →
/notificationsrow-click - Finance — Notification row-click navigation — Overview / Transactions after row-click lands on booking
- Bookings — Notification row-click navigation — Booking sidebar landing zone after row-click
- Tenants — Notification row-click navigation — Tenant profile sidebar when alert carries
tenantId - Inbox — Notification row-click navigation — Bell Inbox
linkdeep-link vs General row-click - Operations — Notification row-click navigation — Turnover-week alerts that row-click into Bookings first
- Listings — Notification row-click navigation — Property or unit sidebar when alert carries
listingIdorpropertyId - Utilities — Notification row-click navigation — Overage payment overdue alerts after bill cycle
- Sales — Notification row-click navigation — Channel-import alerts before Multicalendar review
- Analytics — Notification row-click navigation — Month-range KPI charts after row-click opens booking context
- AI Chat — Notification row-click navigation — Verify assistant-cited alerts by row-click before operational follow-up
- Audit — Notification row-click navigation — Discounts / Manual Blocks month-end review after row-click
- Legacy
/propertiesURLs — Notification row-click navigation — Legacy bookmarks that land in Listings during alert triage - Booking engine details — Notification row-click navigation — Engine-sourced alerts before Full integration payload edits
- Open the related booking, tenant, or listing — Target field order on full inbox
- Pending manual in-payments (approval queue) — Pending manual in-payment row-click → Approve
- Payment overdue alerts (in-app) — Payments category operator rows
- Notification triage — Step 4 — Canonical row-click before Step 5
- Common Workflows — WhatsApp per-booking messaging —
New WhatsApp message from …→ bell Inbox / Communication - Processing a New Booking — Notification row-click navigation — Booking created / Payment received on Step 6
- Cancelling a Booking — Notification row-click navigation — Pre-cancel payment overdue on Step 2
- Managing a Check-in — Notification row-click navigation — Move-in alerts on Step 3
- Managing a Check-out — Notification row-click navigation — Departure-week alerts on Step 6
- Entering Monthly Utility Bills — Notification row-click navigation — Utility payment overdue on Step 4
- Handling a Late Payment — Notification row-click navigation — payment overdue on Step 1 after alert row-click
- Portfolio KPI review — Notification row-click navigation — Month-end alert batch on Step 7
- Notification triage — Notification row-click navigation — Payments row-click on Step 4
- Manual block hygiene — Notification row-click navigation — Stale alerts after Step 5 hold cleanup
- Onboarding a New Property — Notification row-click navigation — First Payment received on Step 7 go-live
- Using in-app support — Notification row-click navigation — Self-serve alert triage before filing
- Resetting a Management User Password — Notification row-click navigation — Lockout-delayed payment overdue after Step 3
Payment alert to receivables triage
Payments category row-click on /notifications pairs with Notification triage — Step 4 before portfolio Debt Aging — hub parity: Common Workflows — Payment alert to receivables triage. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Payment alert to receivables triage — Hub matrix (
notifications-row-navigate-to-booking-detail.png,notifications-row-navigation-flow.mp4,finance-overview-debt-aging-walkthrough-flow.mp4) - Dashboard — Payment alert to receivables triage — Total Debt KPI after alert row-click
- Bookings — Payment alert to receivables triage — Payment Plan / Transactions on opened booking
- Tenants — Payment alert to receivables triage — With Debt cross-check on tenant profile
- Inbox — Payment alert to receivables triage — payment overdue on General before WhatsApp chase
- Operations — Payment alert to receivables triage — Unpaid move-in lines before key handover on Check-in & Check-out
- Listings — Payment alert to receivables triage — Property Payments Active portal charges on listing bookings
- Utilities — Payment alert to receivables triage — Utility overage lines behind overdue alerts
- Sales — Payment alert to receivables triage — Channel-import schedules behind overdue alerts
- Analytics — Payment alert to receivables triage — Revenue trend may lag until receivables clear
- AI Chat — Payment alert to receivables triage — Validate assistant debt answers after receivables triage
- Audit — Payment alert to receivables triage — Discounts review when receivables lag behind goodwill lines
- Legacy
/propertiesURLs — Payment alert to receivables triage — Collections on bookings tied to redirected properties - Booking engine details — Payment alert to receivables triage — Engine-sourced schedules behind overdue alerts
- Payment overdue alerts (in-app) — Payments category operator rows
- Pending manual in-payments (approval queue) — Pending manual in-payment row-click → Approve
- Notification triage — Step 4 — Row-click before bulk Mark all as read
- Finance — Payment alert to receivables triage — Overview → Debt Aging after single-booking triage
- Finance debt receivables triage — Portfolio Top debtors when alert batch needs rank
- Processing a New Booking — Payment alert to receivables triage — Upcoming vs Ongoing on Step 5 / Step 6
- Cancelling a Booking — Payment alert to receivables triage — Pre-cancel payment overdue on Step 2
- Managing a Check-in — Payment alert to receivables triage — Move-in alerts on Step 3
- Managing a Check-out — Payment alert to receivables triage — Departure-week alerts on Step 6
- Entering Monthly Utility Bills — Payment alert to receivables triage — Utility payment overdue on Step 4
- Handling a Late Payment — Payment alert to receivables triage — payment overdue on Step 1 after alert row-click
- Portfolio KPI review — Payment alert to receivables triage — Month-end alert batch on Step 7
- Notification triage — Payment alert to receivables triage — Payments row-click on Step 4
- Manual block hygiene — Payment alert to receivables triage — Stale alerts after Step 5 hold cleanup
- Onboarding a New Property — Payment alert to receivables triage — First Payment received on Step 7 go-live
- Using in-app support — Payment alert to receivables triage — Self-serve alert triage before filing
- Resetting a Management User Password — Payment alert to receivables triage — Lockout-delayed payment overdue after Step 3
- FAQ — Payment alert to receivables triage — Alert-type contrast table
- FAQ — Payment alert to receivables triage hub — Canonical Payments category row-click symptom table
- Manual block hygiene — Directory list load failures — Audit → Manual Blocks Retry before row scan (Step 1)
- Cancelling a Booking — Directory list load failures — Whole-module Bookings Retry before cancel execution (Step 4)
- Managing a Check-out — Directory list load failures — Departure-week directory Retry on Step 1
- Onboarding a New Property — Directory list load failures — Listings portfolio Retry on Step 7 go-live verify
- Processing a New Booking — Directory list load failures — Bookings / /notifications Retry before import triage (Step 1)
Month-end invoicing (fixed date)
Alert cleanup on /notifications before month-end bulk Issue allocation — pair Notification triage — Step 5 with fixed Invoice date saved in Settings → Invoicing. Hub parity: Common Workflows — Month-end invoicing (fixed date). Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Month-end invoicing (fixed date) — Hub matrix (
settings-invoicing-invoice-date-toggle.png,finance-transactions-fixed-invoice-date-banner.png,finance-transactions-bulk-toolbar-fixed-invoice-date-banner.png) - Invoicing — Default invoice date — Account-wide toggle + Save
- Common Workflows — Bulk Hostkit invoicing — Issue allocation after fixed date is saved
- List load and read actions — Clear alerts before Finance → Transactions bulk export
- Notification triage — Month-end invoicing (fixed date) — Step 5 alert cleanup mesh
- Processing a New Booking — Month-end invoicing (fixed date) — First-month bulk export after confirmation (Step 6b)
- Handling a Late Payment — Month-end invoicing (fixed date) — Collections batch during Step 6b
- Portfolio KPI review — Month-end invoicing (fixed date) — Step 7 sign-off mesh
- Notification triage — Month-end invoicing (fixed date) — Alert cleanup before bulk Issue allocation (Step 5)
- Entering Monthly Utility Bills — Month-end invoicing (fixed date) — Finish Missing data + overage Pending (Steps 4b–5)
- Manual block hygiene — Month-end invoicing (fixed date) — Clear stale holds before Issue allocation (Step 5)
- Using in-app support — Month-end invoicing (fixed date) — Self-serve before filing wrong-date tickets
- Resetting a Management User Password — Month-end invoicing (fixed date) — Lockout-delayed month-end export after Step 3
- FAQ — Month-end invoicing (fixed date) hub — Alert cleanup before month-end bulk Issue allocation with fixed Invoice date symptom table
Bulk Hostkit invoicing
Clear payment received / Pending manual in-payment alerts before month-end bulk Issue allocation — row-click lands on booking Transactions for approval first. Hub parity: Common Workflows — Bulk Hostkit invoicing. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Bulk Hostkit invoicing — Hub matrix (
finance-transactions-bulk-selection-bar.png,settings-invoicing-hostkit-series.png) - Common Workflows — Month-end invoicing (fixed date) — Fixed Invoice date before bulk Issue allocation
- Settings > Invoicing — Hostkit invoice series — Required FR code before Issue allocation
- Finance — Invoice automation — Bulk Issue allocation / Invoice selected toolbar
- Finance — Issuing credit notes (integrated invoicing) — Issue credit notes (N) after invoiced Reject / Revert
- Open the related booking, tenant, or listing — Alert row-click before bulk export
- Finance — Bulk Hostkit invoicing — Transactions toolbar reference
- Processing a New Booking — Bulk Hostkit invoicing — First-month Issue allocation after confirmation (Step 6b)
- Handling a Late Payment — Bulk Hostkit invoicing — Collections month-end mesh (Step 6b)
- Portfolio KPI review — Bulk Hostkit invoicing — Step 7 month-end sign-off
- Managing a Check-in — Bulk Hostkit invoicing — Move-in Pending mesh (Step 6b)
- Managing a Check-out — Bulk Hostkit invoicing — Departure-week mesh (Step 6b)
- Onboarding a New Property — Bulk Hostkit invoicing — First month-end on new inventory
- Cancelling a Booking — Bulk Hostkit invoicing — Settlement bulk export (Step 6b)
- Notification triage — Bulk Hostkit invoicing — Alert cleanup before bulk export (Step 5)
- Entering Monthly Utility Bills — Bulk Hostkit invoicing — Finish Missing data + overage Pending (Steps 4b–5)
- Manual block hygiene — Bulk Hostkit invoicing — Clear stale holds before Issue allocation (Step 5)
- Using in-app support — Bulk Hostkit invoicing — Self-serve Hostkit pacing before filing tickets
- Resetting a Management User Password — Bulk Hostkit invoicing — Lockout-delayed month-end export after Step 3
- FAQ — Bulk Hostkit invoicing slow — Hostkit HTTP 429 pacing and refresh-before-reissue habit
- FAQ — Bulk Hostkit invoicing hub — Alert cleanup before month-end bulk Issue allocation Hostkit pacing symptom table
Directory list load failures
/notifications first-fetch failures show Failed to load notifications. + Try again in the main panel — use Retry before Notification triage — Step 4 row-click opens a booking. Hub parity: Common Workflows — Directory list load failures. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Directory list load failures — Hub matrix (
notifications-module-load-failure.png) - List load and read actions — Try again on first-fetch failure
- Processing a New Booking — Directory list load failures — Confirmation alert row-click on Step 1 / Step 6
- Notification triage — Step 4 — Row-click after list loads
- Getting Started — Lockout catch-up after password recovery — /notifications Retry after lockout before alert triage
- FAQ — Directory list load failures — Whole-module vs unread-empty state
- FAQ — Directory list load failures hub —
/notificationsTry again before alert row-click symptom table - Glossary — Directory list load failures hub — Surface table + per-guide/module mesh reciprocal hub
Partly collected security deposit
Deposit shortfalls pair with Finance — Deposits status summary cards and Bookings — Deposit tab. Hub parity: Common Workflows — Partly collected security deposit. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Partly collected security deposit — Hub matrix when Paid on the deposit is above zero but below Amount
- Finance — Deposit lifecycle status cards — Partial paid card for portfolio triage (#2091)
- Finance — Deposit status filter — Other filters → Deposit status → Partial paid on Bookings and Finance (#2090)
- Operations — Tickets toolbar search — Paste the full sequential ticket ID (for example
S259,T27) in toolbar Search (#2074) - FAQ — Find a ticket by its ID — Paste the full sequential ticket ID (for example
S259,T27) in Operations → Tickets toolbar Search (#2074) - FAQ — Skip automatic check-in/out tickets for one booking — Turn off Use unit contract rents and other contract details on Add booking to reveal CI/CO ticket checkboxes (#1140)
- FAQ — Same-day turnovers — Check-out + check-in on one unit same day: Operations → Check-in & Check-out, Timeline / Multicalendar, turnover tickets
- FAQ — Manual payments after Delete Booking — Delete Booking hides manual/provider_platform rows on Finance → Transactions; vIBAN and credit card stay visible (#1897)
- Glossary — Directory list load failures — First-fetch directory failures show Retry / Try again; distinct from filter-empty states and booking-sidebar tab errors
- Glossary — Vacant Unit Preference — Include manual blocks counts operator holds as free on Dashboard / Sales vacancy surfaces (#1427)
- FAQ — Communication or Tickets load failure — Tab-scoped Refresh (Communication) or Retry (Tickets); other booking sidebar tabs stay usable
- Bookings — Deposit tab — Partially paid badge and remaining helper on a single reservation
- FAQ — Partly collected security deposit — Distinct from Partial Paid rent on Payment Plan
- Finance — Deposit lifecycle status cards — Deposit lifecycle status row (#2091)
- Glossary — Deposit lifecycle status —
depositStatuspill vocabulary (Partial Paid vs rent Partial Paid) - Finance — Deposit lifecycle status cards — Deposit lifecycle status row on Finance → Deposits; click Partial paid for collection shortfalls (#2091)
- Manual block hygiene — Partly collected security deposit — Partial paid card when debt KPIs stay high after holds cleared (Step 5)
- Resetting a Management User Password — Partly collected security deposit — Lockout-delayed deposit triage after Step 3
- Using in-app support — Partly collected security deposit — File Finance module tickets when partial filter or badge behaviour is wrong
Booking sidebar tab load failures
Notification triage — Step 4 row-click opens a booking — if Communication or Tickets fails inside the sidebar, use tab Refresh / Retry while other tabs stay usable. Whole /notifications Failed to load notifications. is Directory list load failures — not tab-scoped recovery. Hub parity: Glossary — Booking sidebar tab load failures hub · Common Workflows — Booking sidebar tab load failures. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Booking sidebar tab load failures — Hub matrix (
notifications-row-navigate-to-booking-detail.png,bookings-detail-communication-tab-whatsapp-thread.png) - Glossary — Booking sidebar tab load failures hub — Surface table + per-guide/module mesh reciprocal hub
- Notification triage — Step 4 — Tab recovery after payment alert row-click
- Notification row-click navigation — Row-click target before tab failure
- Bookings — Sidebar tab load failures — Module reference
- Using in-app support — Booking sidebar tab load failures — File Bookings module ticket when recovery fails
- FAQ — Communication or Tickets load failure — Symptom table per tab
Finance debt receivables triage
Payments alert batches on /notifications pair with Payment alert to receivables triage before portfolio Debt Aging when you need ranked debtors. Hub parity: Common Workflows — Finance debt receivables triage. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Finance debt receivables triage — Hub matrix (
finance-overview-income-chart-debt-aging.png,finance-overview-debt-aging-walkthrough-flow.mp4) - Payment alert to receivables triage — Single-booking alert triage before portfolio surfaces
- Finance — Finance debt receivables triage — Debt Aging Top debtors canonical surface
- Pending manual receipt approval — Clear amber Pending before Top debtors sign-off
- Dashboard — Finance debt receivables triage — Total Debt headline vs Finance drill-down
- Bookings — Finance debt receivables triage — Payment Plan on opened booking
- Handling a Late Payment — Finance debt receivables triage — Debt Aging on Step 1 before outreach
- Portfolio KPI review — Finance debt receivables triage — Month-end Top debtors on Step 7
- FAQ — Finance debt receivables triage hub — Symptom table for four-surface triage
- Payment overdue alerts (in-app) — Ongoing/Ended row-click entry
- Notification row-click navigation — Row-click before portfolio KPI read
Finance Income status drill-down
Payments alert batches pair with Payment alert to receivables triage before you read Income segments for portfolio rank. Hub parity: Common Workflows — Finance Income status drill-down. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Finance Income status drill-down — Hub matrix (
finance-overview-income-status-in-debt-modal.png,finance-overview-income-drill-down-flow.mp4) - Finance debt receivables triage — Debt Aging Top debtors when payment-line modal is not enough
- Finance — Income status drill-down — Stacked Income chart canonical surface
- FAQ — Finance Income status drill-down hub — Symptom table for segment vs Debt Aging
- FAQ — Finance Income status drill-down — Paid / Scheduled / In debt segment-click habit
- Portfolio KPI review — Finance Income status drill-down — Month-end Income reconciliation on Step 7
- Payment overdue alerts (in-app) — Ongoing/Ended row-click entry
- Notification row-click navigation — Row-click before Income segment read
Cash flow forecast drill-down
Payment received alert batches pair with Cash flow forecast to confirm portfolio collections after single-booking triage. Hub parity: Common Workflows — Cash flow forecast drill-down. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Cash flow forecast drill-down — Hub matrix (
finance-overview-cash-flow-all-payments-modal.png,finance-overview-cash-flow-day-view.png,finance-overview-cash-flow-drill-down-flow.mp4) - Finance Income status drill-down — Paid / Scheduled / In debt segments — not collections history
- Finance — Income chart and cash flow forecast — Canonical Cash flow forecast chart surface
- FAQ — Cash flow forecast drill-down hub — Symptom table for collections vs Income / Dashboard
- FAQ — Cash flow forecast drill-down — Month / Day bar-click habit
- Portfolio KPI review — Cash flow forecast drill-down — Month-end collections reconciliation on Step 7
- Payment received alerts (email & in-app) — Alert source rows before collections read
- Notification row-click navigation — Row-click before Cash flow forecast month bar check
Confirmation alert triage
Upcoming Booking created / Payment received / Pending manual in-payment rows on /notifications row-click into Bookings — finish Processing a New Booking — Step 5b / Step 6 before bulk-clear. Canonical path: Notification triage — Confirmation alert triage. Hub parity: Common Workflows — Confirmation alert triage. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Confirmation alert triage — Hub matrix (
notifications-row-navigate-to-booking-detail.png,notifications-row-navigation-flow.mp4) - Dashboard — Confirmation alert triage — Post-login Upcoming alert backlog on bell
- Bookings — Confirmation alert triage — Transactions / Contract Info on Upcoming imports
- Inbox — Confirmation alert triage — WhatsApp thread after Payment received row-click
- Tenants — Confirmation alert triage — Tenant Info / Category on confirmation-week clusters
- Operations — Confirmation alert triage — Turnover prep after confirmation receipts approved
- Listings — Confirmation alert triage — Channel import bookings on go-live properties
- Utilities — Confirmation alert triage — First bill cycle after go-live alerts
- Sales — Confirmation alert triage — Channel-import Upcoming alerts before Channels linking
- Analytics — Confirmation alert triage — Upcoming alerts during month-end KPI review
- AI Chat — Confirmation alert triage — Assistant-cited confirmation backlog before bulk mark-read
- Audit — Confirmation alert triage — Month-end Discounts review after confirmation receipts approved
- Legacy
/propertiesURLs — Confirmation alert triage — First alerts after legacy redirects land in Listings - Booking engine details — Confirmation alert triage — White-label Upcoming alerts before payload sync
- Finance — Confirmation alert triage — Transactions amber Pending before Overview KPI refresh
- Payment received alerts (email + in-app) — Alert source rows
- Notification triage — Step 4 — Row-click entry
- Notification row-click navigation — Navigation target before Approve
- Bookings — Transactions row actions — Approve on confirmation receipts
- FAQ — Processing a New Booking hub — Confirmation-week symptom table
- FAQ — Confirmation alert triage hub — Canonical
/notificationsrow-click symptom table
New inventory to first booking handoff
First Booking created / Payment received alerts on go-live inventory row-click into Bookings — finish Onboarding — Step 7 before Processing a New Booking — Step 5b / 6 and bulk Mark all as read. Hub parity: Common Workflows — New inventory to first booking handoff. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Notification row-click navigation — First Booking created alert triage
- Confirmation alert triage — Upcoming confirmation alerts on new property
- Bookings — New inventory to first booking handoff — First reservation sidebar tabs
- Onboarding a New Property — Step 7 — Upstream go-live verify
- Processing a New Booking — Step 5b / Step 6 — Canonical confirmation gates
- Common Workflows — New inventory to first booking handoff — Hub matrix (
notifications-row-navigation-flow.mp4,bookings-add-booking-modal.png) - Property setup to first arrival handoff — Downstream arrival-week alerts
- FAQ — New inventory to first booking handoff — Symptom table for property wizard → first reservation
Property setup to first arrival handoff
Arrival-week payment overdue and access alerts on first go-live reservations row-click into Bookings / Operations — finish Onboarding a New Property — Step 7 before you bulk Mark all as read. Hub parity: Common Workflows — Property setup to first arrival handoff. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Notification row-click navigation — Arrival/access alerts on first Upcoming stay
- Operations — Property setup to first arrival handoff — Check-in & Check-out after alert triage
- Bookings — Property setup to first arrival handoff — First reservation sidebar tabs
- Onboarding a New Property — Step 7 — Upstream go-live verify
- Managing a Check-in — Step 1 — Downstream arrival-week entry
- Common Workflows — Property setup to first arrival handoff — Hub matrix (
workflows-operations-check-in-out-planning-view.png,listings-property-edit-access-lockers-tab.png) - Confirmation alert triage — First Booking created alerts before arrival week
- FAQ — Property setup to first arrival handoff — Symptom table for go-live → first arrival week
Confirmation to check-in handoff
/notifications row-click on Upcoming Booking created / Payment received alerts opens Bookings — finish Processing a New Booking — Step 5b / Step 6 before ~7-day arrival planning. Hub parity: Common Workflows — Confirmation to check-in handoff. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Notification row-click navigation — Row-click on
/notificationsbefore mark-read - Confirmation alert triage — Canonical inbox pairing for Upcoming alerts
- Bookings — Confirmation to check-in handoff — Contract Info portal gates on Upcoming imports
- Managing a Check-in — Step 1 — Downstream arrival-week entry
- Common Workflows — Confirmation to check-in handoff — Hub matrix (
bookings-detail-contract-method-of-payments.png,workflows-operations-check-in-out-planning-view.png,booking-lifecycle-status-tabs-flow.mp4) - Processing a New Booking — Step 6 — Upstream portal sanity before handoff
- Pending manual receipt approval — Step 5b confirmation receipts before handoff
- FAQ — Confirmation to check-in handoff — Symptom table for Upcoming → arrival week
Check-in to check-out handoff
/notifications payment overdue row-click on Ongoing stays during departure week should open Managing a Check-out — Step 1 — not revisit Managing a Check-in prep after keys handed over. Hub parity: Common Workflows — Check-in to check-out handoff. Full pairing matrix: notifications-section-cross-reference · Module cross-reference.
- Payment overdue alerts — Ongoing stay row-click ~7 days from departure
- Notification row-click navigation — Row-click before mark-read on departure-week alerts
- Bookings — Check-in to check-out handoff — Booking detail after alert row-click
- Operations — Check-in to check-out handoff — Check-outs pill after row-click
- Managing a Check-in — Step 4 — Upstream keys handed over
- Managing a Check-out — Step 1 — Downstream departure-week entry
- Common Workflows — Check-in to check-out handoff — Hub matrix (
operations-check-in-out-check-outs-next-7-days.png,bookings-timeline-view.png) - Notification triage — Check-in to check-out handoff — Canonical inbox pairing (Step 4)
- FAQ — Check-in to check-out handoff — Symptom table for Ongoing → departure week
Check-out final utilities handoff
Departure-week utility payment overdue alerts on /notifications pair with Notification triage — Check-out final utilities handoff (Step 4 row-click) before Managing a Check-out — Step 6. Hub parity: Common Workflows — Check-out final utilities handoff. Distinct from Check-out collections before refund (rent/fee alerts). Full pairing matrix: notifications-section-cross-reference · Module cross-reference.
- Payment overdue alerts — Departure-week utility overage row-click
- Notification row-click navigation — Row-click before mark-read on utility overage alerts
- Notification triage — Check-out final utilities handoff — Canonical inbox pairing (Step 4)
- Entering Monthly Utility Bills — Step 4 — Confirm overage posted before refund queue
- Bookings — Check-out final utilities handoff — Booking detail after alert row-click
- Managing a Check-out — Step 6 — Settlement verification before refund
- Common Workflows — Check-out final utilities handoff — Hub matrix (
notifications-row-navigate-to-booking-detail.png,utilities-allocations-review-flow.mp4) - FAQ — Check-out final utilities handoff — Symptom table for final utility overage blocking refund
Same-day turnover coordination
Arrival/access /notifications alerts during turnover week pair with Notification triage — Same-day turnover coordination (Step 4 row-click) before bulk Mark all as read — hub parity: Common Workflows — Same-day turnover coordination. Full pairing matrix: notifications-section-cross-reference · Module cross-reference.
- Common Workflows — Same-day turnover coordination — Hub matrix (
notifications-row-navigate-to-booking-detail.png,bookings-timeline-day-week-month-and-sidebar.mp4) - Payment overdue alerts — Outgoing In Debt vs incoming move-in on turnover week
- Notification row-click navigation — Row-click before mark-read on turnover-week alerts
- Notification triage — Same-day turnover coordination — Canonical inbox pairing (Step 4)
- Bookings — Same-day turnover coordination — Booking detail after alert row-click
- Operations — Same-day turnover coordination — Check-outs / Check-ins after row-click
- Managing a Check-in — Same-day turnover coordination — Check-ins overlap on Step 1 before Step 4
- FAQ — Same-day turnovers — Four-step operator habit
- Glossary — Same-day turnover — Shared-unit vocabulary
Occupancy KPI to block hygiene handoff
Bell scan Vacant Units vs Analytics mismatch on Notification triage — Step 1 pairs with hub Common Workflows — Occupancy KPI to block hygiene handoff before bulk Mark all as read. Hub parity: Common Workflows — Occupancy KPI to block hygiene handoff. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Occupancy KPI to block hygiene handoff — Hub matrix (
dashboard-vacant-units-widget.png,analytics-kpi-occupancy-tab.png,audit-manual-blocks-filter-scroll.mp4) - Notification triage — Step 1 — Vacant Units vs Analytics before mark-read
- Dashboard — Occupancy KPI to block hygiene handoff — Post-login vacancy widget
- Payment alert to receivables triage — payment overdue contrast — not hold hygiene
- Manual block hygiene — Downstream Audit pass
- FAQ — Occupancy KPI to block hygiene handoff hub — Symptom table for bell scan occupancy dip
- Managing a Check-in — Occupancy KPI to block hygiene handoff — Timeline overlap from stale holds on Step 1
- Managing a Check-out — Occupancy KPI to block hygiene handoff — Calendar bars persist after Step 7
- Cancelling a Booking — Occupancy KPI to block hygiene handoff — Availability not restored on Step 5
- Entering Monthly Utility Bills — Occupancy KPI to block hygiene handoff — Dashboard vs Analytics vacancy mismatch on Step 5
- Notification triage — Occupancy KPI to block hygiene handoff — Vacant Units vs Analytics on Step 1
- Resetting a Management User Password — Occupancy KPI to block hygiene handoff — Lockout-delayed KPI review after Step 3
- Using in-app support — Occupancy KPI to block hygiene handoff — Calendar edit blocked after block hygiene
- Handling a Late Payment — Occupancy KPI to block hygiene handoff — Vacant Units vs Multicalendar holds on Step 1
WhatsApp per-booking messaging
Messages category New WhatsApp message from … rows on /notifications pair with bell Inbox or Bookings → Communication — finish row-click triage before bulk Mark all as read. Hub parity: Glossary — WhatsApp per-booking messaging hub · Common Workflows — WhatsApp per-booking messaging. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — WhatsApp per-booking messaging — Hub matrix (
bookings-detail-communication-tab-whatsapp-thread.png,inbox-module-overview.png,inbox-module-triage-flow.mp4) - Glossary — WhatsApp per-booking messaging hub — Surface table + per-guide/module mesh reciprocal hub
- Dashboard — WhatsApp per-booking messaging — Bell Inbox sub-tab vs General on post-login scan
- Bookings — WhatsApp per-booking messaging — Communication tab composer with Payment Plan context
- Inbox — WhatsApp per-booking messaging — Cross-booking triage and bell Inbox sub-tab
- Tenants — WhatsApp per-booking messaging — Tenant profile after Inbox name click
- Finance — WhatsApp per-booking messaging — Collections outreach with Transactions visible
- Operations — WhatsApp per-booking messaging — Maintenance ticket threads on Communication
- Listings — WhatsApp per-booking messaging — Go-live property tenant threads after channel import
- Utilities — WhatsApp per-booking messaging — Utility overage bill questions on Communication
- Sales — WhatsApp per-booking messaging — Channel-import message backlog during Multicalendar review
- Analytics — WhatsApp per-booking messaging — Month-end message backlog during KPI review
- AI Chat — WhatsApp per-booking messaging — Assistant-cited threads before operational follow-up
- Audit — WhatsApp per-booking messaging — Month-end communication review after Discounts audit
- Legacy
/propertiesURLs — WhatsApp per-booking messaging — Legacy bookmarks during message triage - Booking engine details — WhatsApp per-booking messaging — Engine-sourced tenant threads before payload sync
- Dashboard bell vs. full module — Bell Inbox sub-tab vs full inbox
- Open the related booking, tenant, or listing — Row-click target when message alert carries
bookingIdonly - Notification row-click navigation —
New WhatsApp message from …→ bell Inbox / Communication - Common Workflows — Notification row-click navigation —
New WhatsApp message from …on/notificationsvs bell Inbox - Notification triage — WhatsApp per-booking messaging — Message pings on bell Inbox /
/notifications - Handling a Late Payment — WhatsApp per-booking messaging — Collections outreach on Step 3
- Managing a Check-in — WhatsApp per-booking messaging — Arrival-week threads before Step 4
- Managing a Check-out — WhatsApp per-booking messaging — Departure settlement on Step 6
- Processing a New Booking — WhatsApp per-booking messaging — Confirmation follow-up on Step 6
- Cancelling a Booking — WhatsApp per-booking messaging — Void outreach before Step 4
- Entering Monthly Utility Bills — WhatsApp per-booking messaging — Overage bill questions on Step 4
- Portfolio KPI review — WhatsApp per-booking messaging — Month-end message backlog on Step 7
- Manual block hygiene — WhatsApp per-booking messaging — Blocked-date questions on Step 3
- Onboarding a New Property — WhatsApp per-booking messaging — First tenant threads on Step 7 go-live
- Using in-app support — WhatsApp per-booking messaging — Self-serve Inbox / Communication before filing
- Resetting a Management User Password — WhatsApp per-booking messaging — Lockout-delayed bell Inbox after Step 3
- FAQ — WhatsApp per-booking messaging hub — Canonical
/notificationsmessage alert row-click symptom table
Bot reasoning (audit)
Canonical /notifications bot-related alert rows. Hub parity: Glossary — Bot reasoning (audit) hub · Common Workflows — Bot reasoning (audit). Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Bot reasoning (audit) — Hub matrix (
bookings-detail-communication-tab-bot-reasoning-expanded.png) - Glossary — Bot reasoning (audit) hub — Surface table + per-guide/module mesh reciprocal hub
- Bookings — Bot reasoning (audit) — Canonical Communication Reasoning control
- ChatBot settings — Read-only audit vs editable persona / IF/THEN
ChatBot settings
Account Settings → ChatBot pairs with Communication thread review — canonical /notifications bot-related alert rows. Hub parity: Glossary — ChatBot settings hub · Common Workflows — ChatBot settings. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — ChatBot settings — Hub matrix (
settings-chatbot-tab-overview.png,settings-chatbot-status-bot-connected.png,settings-chatbot-save-rule-flow.mp4) - Glossary — ChatBot settings hub — Surface table + per-guide/module mesh reciprocal hub
- ChatBot settings — Persona, IF/THEN rules, Status Bot pairing
- Glossary — Bot reasoning (audit) hub — Thread audit after rule changes
Rent reduction after invoicing
Payment overdue or Payment received row-click may land on a booking whose confirmation month is already invoiced — finish Transactions → Approve and Contract Info → Change monthly rent before bulk mark-read. Pair Bulk Hostkit invoicing when relief needs Not issued credit note rows. Hub parity: Common Workflows — Rent reduction after invoicing. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Rent reduction after invoicing — Hub matrix (
bookings-detail-change-monthly-rent-modal.png,bookings-rent-reduction-invoiced-floor-flow.mp4) - Bookings — Changing contract dates and rent — Contract Info repricing entry point
- Bookings — Contract Values tab — Per-line Edit amount under the same floor
- Finance — Invoiced floor and rent edits — Why edits start on the booking, not Finance → Transactions
- Payment overdue alerts in-app — Row-click before Change monthly rent
- Processing a New Booking — Rent reduction after invoicing — Confirmation month already invoiced on Step 3
- Handling a Late Payment — Rent reduction after invoicing — Collections goodwill after Step 4
- Portfolio KPI review — Rent reduction after invoicing — Month-end repricing sign-off on Step 7
- Cancelling a Booking — Rent reduction after invoicing — Settlement repricing during Step 2b
- Managing a Check-in — Rent reduction after invoicing — Pre-move-in goodwill
- Managing a Check-out — Rent reduction after invoicing — Departure-week goodwill adjustments
- Notification triage — Rent reduction after invoicing — Row-click to invoiced booking on Step 4
- Entering Monthly Utility Bills — Rent reduction after invoicing — Month-end bill cycle on Step 5
- Manual block hygiene — Rent reduction after invoicing — Hold cleanup on Step 5
- Using in-app support — Rent reduction after invoicing — Self-serve before filing tickets
- Resetting a Management User Password — Rent reduction after invoicing — Lockout-delayed repricing after Step 3
- FAQ — Rent reduction after invoicing hub — Alert row-click landing on invoiced booking before repricing symptom table
Portfolio segmentation by tenant category
Segment filters pair with Settings > Tenant categories and Portfolio KPI review — Step 6. Hub parity: Common Workflows — Portfolio segmentation by tenant category. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Common Workflows — Portfolio segmentation by tenant category — Hub matrix when payment alerts cluster on one tenant segment
- Finance — Tenant category filter — Scope In Debt triage by segment after row-click from payment alerts
- Bookings — Other filters — Tenant category when alert volume suggests one cohort
- Tenants — Tenant category filter — Profile-count cross-check before bulk alert dismissal
- Portfolio KPI review — Step 6 — Segment weak metrics during month-end alert review
Key glossary terms
Glossary rows pair with Glossary cluster cross-reference. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
-
Booking detail sidebar tab load failures — Communication / Tickets Refresh and Retry after row-click navigation
-
Credit note (payment reject/revert) — Payment alerts that need Reject / Revert with invoiced-line follow-up
-
Deposit dispute — Deposit-related alerts during check-out triage
-
Glossary — End-of-Booking cost split — Charge Time → End of Booking splits daily overage across every occupied unit; still-staying roommates stay in the denominator (#2111)
-
Operations — Property-level ticket search — Property-name matches share the top relevance tier with unit hits; building-scoped rows float first under an active Property filter (#2089)
-
Glossary — Change history — Operator-initiated edits on Listings setup and Bookings Changelog; create-time defaults excluded (#2093)
-
FAQ — Booking Changelog scope — Operator-initiated edits only; create-time defaults excluded (#2093)
-
Glossary — Archived booking ledger visibility — Delete Booking hides manual/provider_platform rows on Finance → Transactions; vIBAN and credit card stay visible (#1897)
-
Bookings — Provider platform payment — Non-rejected provider platform in-payment blocks Delete Booking until Reject or assign (#2076)
-
FAQ — Delete Booking on integration reservation — Clear pending provider platform in-payment with Reject or assign before soft-archive (#2076)
-
Listings — Property edit sidebar pills — Setup / Full integration / Photos pills on property and unit edit sidebars; replaced the old Go to details shortcut (#2082)
-
Glossary — Finance tenant category cache refresh — Recategorizing a tenant on Tenants → Tenant Info force-refreshes Finance caches so Contract Values, Overview, and Deposits filters match within seconds (#2088)
-
FAQ — Finance tenant category filter parity — Finance Other filters drawer lists segments on cached bookings only; mirror Bookings / Tenants when a segment is missing
-
FAQ — Assign tenant category for direct booking — Add booking has no category field; assign on Tenants → Tenant Info or + Create New → Tenant before contract mail
-
Glossary — SIMAR water contract ID — SIMAR (Loures e Odivelas) water bills use Cód. Local in Connections — not Nº de Contador; leading zeros stripped (#2110)
-
FAQ — SIMAR water bill property match — Cód. Local in Connections — not Nº de Contador; strip leading zeros (#2110)
-
Glossary — Per-booking maintenance ticket opt-out — Add booking checkboxes skip automatic CI/CO tickets for one reservation only; property rule unchanged (#1140)
-
FAQ — Cancel Booking vs Delete Booking — Cancel for real stays with settlement; Delete soft-archives mistaken/test rows (#1897 / #2076)
-
Glossary — Archived property — Archive retires a building to Listings → Archived without deleting bookings; distinct from Delete Booking (reservation soft-archive) — Listings — Archived properties
-
FAQ — Archive a property — Edit property sidebar Archive / Unarchive on Listings; building-level — not Delete Booking or Cancel booking
-
FAQ — Portfolio retirement decisions — Archive property (building) vs Cancel booking vs Delete Booking (reservation soft-archive) — three-way decision table
-
Deposit lifecycle status —
depositStatuspill vocabulary when Payments alerts follow deposit shortfalls -
Finance — Deposit status filter — Other filters → Deposit status multi-select on Bookings and Finance (#2090)
-
Invoiced floor (rent) — Payment alerts that follow mid-stay repricing blocked below exported rent months
-
FAQ — Bulk Hostkit invoicing slow — Vivin paces Hostkit API calls and retries HTTP 429 during bulk Issue allocation / Invoice selected; refresh Transactions before re-issuing
-
Tenant category — Bookings, Finance, and Tenants segmentation when Payments alerts cluster on one cohort
-
Notification row navigation — Bell rows that deep-link into bookings, Finance, or Inbox
-
FAQ — Notification row-click navigation — On
/notifications, row click marks unread then openslink,bookingId,tenantId,listingId, orpropertyId(first match); Dashboard bell General rows stay in-panel unlesslinkis set -
FAQ — Phone shows Operations only — Mobile phone user agent locks operators with Operations access to
/operations; iPads and narrow desktop browsers keep the full module list -
FAQ — AI token usage — Poll GET /ai-usage / GET /ai-usage/summary with management JWT;
landlord_chat+utility_bill_extraction; no management UI screen yet -
FAQ — Tenant contract signing blocked — No PDF yet, mandatory Your Details gates, category locks, or Lease purpose; portal signing vs paper upload on Contract Info
-
FAQ — Automatic check-in email — Trigger matrix, 15-day cutoff, paper upload vs portal signing, Nuki-only toggle, Send / Resend on Contract Info
-
FAQ — WhatsApp and email per booking — Bookings → Communication tab when tenant chatbot is enabled; Inbox for portfolio-wide triage
-
FAQ — Deposit missing on Finance Deposits — Default ~3 months date range; clear or widen before triaging older move-outs or dispute row actions
-
FAQ — Analytics (KPI workspace) — Portfolio KPIs vs Sales/Listings/Dashboard; load-failure Try again
-
FAQ — Lower rent below invoiced — Change monthly rent clamps and Contract Values → Edit amount blocks net below exported invoice totals; use credit notes in accounting when you truly need a reduction
-
FAQ — Reject or revert an incoming payment — Reject pending rows or Revert confirmed ones; Finance → Transactions uses Reject selected bulk-only; modals warn about credit notes when Finance already invoiced
-
FAQ — Finance Income status drill-down — Overview Income chart (Paid / Scheduled / In debt); click a segment for month-scoped payment-line modal; Debt Aging for booking-level receivables
-
FAQ — Permission denied toast — Red You do not have permission to perform this action. toast when RBAC blocks a save; fix in Users → Role Permissions
-
FAQ — Bookings that owe money — Top debtors and overdue buckets on Finance → Overview; Total Debt KPI is not a table
-
FAQ — Fixed rent on variable unit — Variable listing + equal rent every contract month → booking stores fixed headline Monthly rent; payment plan unchanged
API & companion guides
API bullets pair with API Reference hub. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- API Reference — Webhooks & Notifications — Partner HTTP callbacks (distinct from this in-app inbox) when channel imports change booking or calendar state
- AI usage API — Internal LLM token ledger (
GET /ai-usage/summary) when month-end alert triage pairs with Portfolio KPI review — Step 7; not tenant billing
Module documentation hubs
Module hub bullets pair with Modules — Module cross-reference. Full pairing matrix: Notifications section cross-reference · Module cross-reference.
- Notifications module — Full
/notificationshistory with search, filters, and row-click navigation (this page) - Utilities module — Bills Included ceiling model, Connections, AI bill upload, and tenant overage charges on payment plans (hub)
- Operations module — Maintenance tickets, cash flows, check-in/out coordination, Draft ticket queues, and linked cash flows (hub)
- Dashboard module — Post-login Today, Total debt, Vacant Units, and forecast KPI snapshot with bell notification triage (hub)
- Analytics module — Month-range portfolio KPI charts (Overview, Revenue, Occupancy, ADR, RevPAR, Maintenance) with rankings and heatmaps (hub)
- Listings module — Property wizard, Channels tab, Archived inventory, and unit management (hub)
- Properties workspace — Legacy
/propertiesURL redirects into Listings (hub) - Booking engine details — Rich marketplace payload editor via the Full integration pill (hub)
- Finance module — Portfolio ledgers (Overview, Income, Contract Values, Transactions, Payouts, Deposits) with payment approval and deposit settlement (hub)
- Tenants module — Tenant directory, profile sidebars, With Debt segmentation, and table expand for linked bookings (hub)
- Sales module — Portfolio availability, monthly rent editing, and channel manager connections (hub)
- Inbox module — Portfolio-wide WhatsApp workspace with Dashboard bell Inbox sub-tab deep links (hub)
- AI Chat module — Vivin-internal AI Assistant using Landlord MCP tools for portfolio Q&A (hub)
- Audit module — Portfolio-wide Manual Blocks and Discounts contract-value review (hub)
- Account Settings — Workspace-wide financial policies, templates, integrations, and operational defaults (hub)
- API Reference hub — Partner HTTP contracts, Swagger onboarding, and partial vs full feeds (hub)