Notifications

Where notifications reach you, workspace-level reminder timing, and what is and is not configurable today.

Watch how it works

On this page

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 where notifications reach you, the workspace-level reminder timing you can configure, and what the system decides for you.

Where notifications reach you

A notification reaches each recipient in up to two places:

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.
Mobile push: Turned on when you install the mobile app and allow notifications. Anything waiting for you to act reaches your phone: a workflow step assigned to your role or sent back to you for changes, a payment or expense waiting for your verification, a reminder that a step's deadline is near or that it was escalated to you, and a to-do item assigned to you, as well as new maintenance requests, recurring tasks that are due, overdue-rent follow-ups and a payment you recorded being approved. Some things that are only for your information stay in the bell, such as a court order being closed, a sale completing, a to-do list being shared with you, or someone else ticking off an item on it.

About mobile push in particular:

A push arrives in the language your app is set to, and follows a language change you make inside the app. Versions older than 1.0.4 always receive Arabic, so update the app if you use it in English.
A push never shows an amount, because its text appears on the lock screen to whoever holds the phone. Open it to see the figure in the app.
Tap an approval to open the task itself and approve it or send it back from your phone. If it belongs to another workspace you are a member of, the app switches to that workspace first.

Email is not one of them. Email carries account messages only: verifying your address, resetting a password, an invitation to a workspace, and subscription invoices. Notifications, rent reminders and workflow escalations are not emailed today.

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.

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.

These roles, together with the escalation recipients below, are also the people who can log follow-ups on a rent task (a call, a visit, a promise to pay). Someone who sets a day on a follow-up gets a notification and a phone alert at 8 in the morning on that day, while the rent is still owed. See Following up on overdue rent.

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. The one exception is Product news on my phone, which covers only our announcements (see Announcements from our team below). If you want fewer pushes, uninstall the mobile app or disable push permissions in your OS settings.
SMS: Not a delivery channel at all today, for inbox notifications or for rent reminders (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.

Announcements from our team

Occasionally a notification appears in the System tab that did not come from anything you or your team did. These are announcements we send: a scheduled-maintenance notice, a security note, a billing change, or a short walkthrough of something new.

They appear in your inbox on web and mobile, in the System tab.
They never send an email or an SMS. Most wait for you in the app. Some we also send to your phone as a notification, and those reach your phone only while Product news on my phone is on.
Product news on my phone is on unless you turn it off. In the mobile app it is under Settings, Notification preferences (version 1.0.4 or later on iPhone, 1.0.5 or later on Android); on the web it is under Settings, Preferences. With it off you still see every announcement in the System tab, only the phone notification stops, and notifications about your tasks and approvals are not affected.
A phone notification from us shows in your app's language: the English version if there is one and your app is in English, otherwise the Arabic. Tapping it opens its link when the link is on our website; otherwise it opens the notifications page, where you will find the link. On older versions it always opens the notifications page.
We never use phone notifications for offers or promotions.
Some carry a link button, often a short video. It opens in a new tab on the web, and in an in-app browser on mobile.
We write them in Arabic, and sometimes add an English version. If you use the app in English and the announcement has an English version, that is the one you see. On mobile this needs version 1.0.4 or later; older versions show the Arabic.
They never reach your residents (the tenants who sign in to the resident portal). They are for you and your team only.
You read, star, and delete them exactly like any other notification.

Apart from the Product news on my phone switch, everything under "What's NOT user-configurable today" above applies to these as well.

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.

The tabs on the notifications page

The inbox groups what you receive into tabs: All, Rent, Maintenance, Leases, Recurring, Payments, To-do, Court orders and System. They are the same tabs in the web app and on the phone.

Two things about them are worth knowing, because both surprise people:

A tab disappears when the part of the system it belongs to is turned off, and comes back the moment it has something unread. Maintenance, Recurring, To-do and Court orders each belong to one part of the system (see Workspaces). Turn that part off and its tab goes, unless it still holds something you have not read: nothing you were sent is ever hidden from you because of a setting somebody changed afterwards. Leases does not work this way, and cannot: that tab also carries contract renewals and terminations, which every workspace has.

"Rent is old enough for court" is a Rent notification, not a Court orders one. It is your own system telling you an installment has aged past your threshold. Nothing has been filed and no court is involved yet. The Court orders tab is for cases that actually exist: an approval waiting on you, a filing being returned, a case being closed.

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.