Notifications

The system pings your team when something needs attention — a payment to verify, a maintenance request to triage, an overdue rent installment. This article covers the three delivery channels, the workspace-level reminder timing you can configure, and what the system decides for you.

The three delivery channels

Every notification fans out across up to three channels per recipient:

• In-app inbox — The bell icon in the top bar and the Notifications page. Every member sees their notifications here regardless of preference; this is the canonical record.
• Email — Sent to the address on the recipient's profile. Used for higher-importance items (overdue rent, escalated workflow steps).
• Mobile push — Registered automatically when you install the mobile app and accept the OS prompt. Used for time-sensitive items where you want the recipient to react now (a new maintenance request, a workflow step that's hit its deadline).

[!info] SMS and WhatsApp delivery aren't enabled on the platform yet. They're on the roadmap for a later release. Don't expect text messages or WhatsApp pings to fire — until that ships, the three channels above are the full surface.

How role-based delivery works

Notifications are addressed to a role, not a specific person. When the system needs to notify "the manager," it looks up every member with the Manager role on the relevant property and sends to all of them.

This means:

• Adding a new member to a role automatically subscribes them to that role's notifications.
• Removing a member from a role automatically unsubscribes them.
• Two managers on the same property both get the same notifications — the system doesn't pick a "primary."

If a role has no members on a property, notifications targeted at that role on that property silently go nowhere. Use the warning in the workflow editor as a sanity check before saving.

Configurable reminder timing (workspace-wide)

Open Settings → Configuration → Notifications. This page is admin-only and applies to every member of the workspace. You're not configuring on/off toggles — you're configuring when the system fires recurring reminders relative to rent, lease, and recurring-task events.

This is the single place to set rent-reminder frequency — the day-counts you enter here are exactly what the reminder system uses, so what you set is what fires.

[!info] Scheduled reminders only. The recipients you pick on this page apply to the scheduled reminders described below. Notifications fired by workflow steps (approvals, reviews, returns) always go to whichever role is assigned to that step in the workflow editor — changing a step's role is what changes who gets those.

Rent reminders

• Rent reminder days — A list of integers like 7, 3, 1. The system fires a reminder that many days before rent is due. Default works for most teams; tighten to 3, 1 if your tenants pay reliably, widen to 14, 7, 3, 1 if collections need a longer drumbeat.
• Rent overdue days — When the rent is past due by these many days, an overdue notification fires. Default usually starts at day 1 — adjust if your business gives a customary grace period.
• Who is notified for rent follow-ups — Pick which roles (built-in or custom) receive the overdue-rent follow-up. Leave it empty to use the default: Property Manager + Admin.

[!info] One rent task per contract. Rent reminders are grouped per contract, not per unit. A multi-unit contract (say a 17-unit commercial lease) shows up as one overdue-rent task — with the total owed and a count of how many units are behind — instead of flooding your Tasks page and the General Manager with one reminder per unit. The same holds when it escalates: one follow-up, one GM alert. Grouping by tenant on the Tasks page still works on top of this.

Escalation timing

• GM escalation days — How many days after a rent installment goes overdue the escalation fires. Default: 14 days. Tune up if your team handles initial collection without senior involvement; tune down if you want senior eyes on every miss.
• Escalation recipients — Which roles receive that escalation. Leave empty for the default: General Manager.

Court eligibility (Ejar)

How many days a rent installment must be overdue before the system flags it as court-eligible, following Ejar's per-cycle policy:

• Short payment cycles (monthly / quarterly) — default 15 days overdue.
• Long payment cycles (semi-annual / annual) — default 30 days overdue.

This is a flag and reminder to your team, not an automatic legal filing — the system never files anything on your behalf.

Lease offer reminders

• Remind before offer expires (days) — Days before a lease offer's expiry date the system nudges your team, so an offer never silently dies. Thresholds like 7, 3, 1 fire one reminder as each is crossed (at least one threshold is required — the reminder can't be switched off).
• Offer-expiry reminder recipients — Offers that are inside an active workflow automatically notify whoever owns the current step (including custom roles). This picker covers offers outside a workflow; empty means the default: Lease Manager + Admin.

Recurring task reminders

• Recurring task reminder days — Days before a recurring task instance's due date the system pings the assignee. For monthly inspections this might be 3 (warn three days ahead); for annual renewals it might be 30, 14, 7.
• Recurring contract reminder days — Same idea for recurring-contract events (e.g. license renewals tied to a property).

What's NOT user-configurable today

A few things users sometimes look for in Settings and won't find — calling them out honestly so you don't hunt:

• Per-user channel preferences — There's no "send me email but not push" toggle per user. Channel delivery is determined by what's available (do you have an email on file? have you installed the mobile app?), not by a personal preference switch. If you want fewer pushes, uninstall the mobile app or disable push permissions in your OS settings.
• SMS/WhatsApp — Not enabled yet (see above).
• Per-notification-type toggles — You can't pick "send me payment verification pings but not maintenance pings." The role-based design assumes if you're in a role, you want everything that role is responsible for.

The intentional trade-off: simpler defaults, fewer support tickets about "why didn't I get notified?" In practice, role design + reminder timing + the recipient pickers cover almost every real-world configuration need.

Tracking what was sent

The Notifications page (/app/notifications or the bell-icon dropdown) lists every notification you've received, with timestamp and link to the originating item. Read/unread state is per-user — marking it read on web also marks it read on mobile.

Hiding tasks you've handled

The Tasks page has a Select button on the right of the filter bar. Click it to enter selection mode, tick the tasks you want out of the way, and choose Hide — they disappear from your list. This is handy for tasks you've dealt with outside the app, or ones you simply don't want cluttering your view.

Hiding is per-user: it only affects your Tasks page. A task assigned to a role several teammates share stays visible to everyone else — hiding it never removes work from a colleague who still needs to act on it.

Nothing is deleted. Toggle Show hidden (same spot, opposite the filters) to switch the list to your hidden tasks, select the ones you want back, and choose Unhide. Most task types are tied to a specific item, so a genuinely new task — a different maintenance request, a new approval — always shows up normally even if you hid an earlier one. Overdue-rent reminders are the exception: they're keyed per contract, so once you hide a contract's rent task it stays hidden for that contract until you unhide it — the underlying reminders and escalations keep running in the background regardless.

Related

• Workflows and approvals
• Roles and permissions
• Money