Notifications
How Urbero tells you something happened — at the bell, in your inbox, or on your phone.
Last updated: 2026-05-10
Urbero notifies you when something changes: a unit moves status, a teammate assigns you a unit, a lease is signed, someone @mentions you. You choose how loud each one is.
The four delivery channels
Every notification can travel on any combination of:
- In-app inbox — the bell icon at the top right. A red dot marks unread.
- Email — to the address on your Urbero profile.
- SMS — to your profile phone number, if set.
- Chat — to your team's chat workspace, if your brokerage has wired one up.
Different rules can use different channels. Example: a new-lease confirmation in email + chat, but a routine status flip in the bell only.
Notification rules (brokerage admin only)
Brokerage admins configure rules at Settings → Notifications. A rule is a sentence:
When a unit moves from status X to status Y, notify these people on these channels.
Recipients
Pick any combination for a rule:
- Agent in charge — the agent named as the unit's owner.
- Assigned agent — every agent with a unit-level assignment.
- All brokerage admins.
- Specific named users — pick teammates by name.
Channels per rule
For each rule, tick any of: in-app, email, SMS, chat. Most rules only need one or two — escalations and signed leases are the typical multi-channel cases.
Default rules
The first time a status change fires for your brokerage, Urbero seeds sensible defaults (for example, "notify the Agent in charge when a unit moves to leases_out"). You can also bootstrap them on the rules card itself. Edit, delete, or add your own.
Why this matters
Without rules, a status change is silent. Rules turn the system from a database into something that actively prompts the right person at the right moment.
Your personal preferences
Every user has a page at Settings → Notifications → Me with one row per event type (unit status changes, @mentions, lease renewal windows, deal stage changes, and a few others). For each event you tick which channels you want — in-app, email, SMS, chat — or untick them all to effectively mute that event for yourself. Defaults are set per event so you only tune what you care about.
These per-user preferences sit on top of the brokerage rules. If a rule says "send on email + chat" but you've unticked email for that event, you'll only get chat.
The bell inbox
The bell in the top bar opens your in-app inbox.
- Click the bell to expand the list.
- Each entry shows what happened, who did it, and a relative date — "Today 8:00 AM", "Yesterday", or "Apr 25 2026" for older items.
- Click an entry to jump to the related unit, deal, or building.
- Click Mark all read to clear the unread badge. A toast appears with Undo if you tapped it by mistake.
The bell only shows in-app deliveries. Email / SMS / chat live in their own places.
Activity digest
The digest is a separate channel from rules — a daily or weekly summary email of what happened in your brokerage.
Brokerage admins manage subscriptions on the same Settings → Notifications page. For each recipient, pick a schedule (daily or weekly) and an email address. Each digest aggregates everything since the recipient's last send: units rented, new deals opened, status changes.
Behind the scenes the digest job runs every hour, but each subscriber only receives an email when their schedule window (24 hours for daily, 7 days for weekly) has elapsed. Flipping from weekly to daily takes effect on the next hour, not the next week.
The cron fires hourly, so a daily subscriber gets an email roughly once per day; weekly subscribers, roughly once per seven days. The exact time is anchored to when your last digest went out.
Mentions feed into your inbox
When a teammate types @yourname in a comment, that lands on a separate /inbox page (sidebar link). See Comments for how mentions work.
Dev / staging behavior
If your environment hasn't been wired up with email and SMS credentials yet (typical for local development), deliveries print to the server console instead of going out. Nothing actually emails or texts — safe by default.
Related
- Comments — how @mentions work and what feeds your /inbox.
- Inventory table — where status changes happen that trigger rules.