How the bell, your personal preferences, company defaults, and escalation rules fit together.
Notifications keep the team ahead of the work: a payment lands, a contract gets signed, a customer texts back. RevolveCore layers personal preferences over company defaults, so you control your own noise level while the company guarantees the critical stuff always gets through.
§The bell and the Notification Center
The 🔔 bell in the masthead (or the screen header on your phone) opens the Notification Center. It updates in realtime, filter chips narrow it by type, and mark-all-read clears the backlog in one tap.
§Your personal preferences
Open Avatar chip → MY SETTINGS → Notifications for your personal grid: 7 notification types across 3 delivery channels, each cell a toggle. RESTORE DEFAULTS puts everything back to the company baseline if you tune yourself into a corner.
The Quiet Hours card silences notifications overnight, with a timezone picker so the hours follow your local clock. A few types always break through quiet hours no matter what: payment failed, new-device sign-in, insurance expiring, and @mentions.
§How a notification decides where to go
Every notification resolves down a chain: your personal preference first, then your role's default, then the company default, then the app baseline. Companies can mark critical types LOCKED ON — a locked-on type beats a personal opt-out, so nobody accidentally silences a failed payment.
§Company defaults (admins)
Admins shape the company layer at Masthead ⚙ gear → Admin Console → COMMUNICATION → Notifications: a 12-category by 4-channel grid where each cell cycles DEFAULT → ON → OFF → LOCKED ON, plus role-scoped defaults, EVENT KILL SWITCHES over 12 named events, and ESCALATION RULES — CC an admin, or escalate to SMS after a set number of minutes — for overdue invoices, failed payments, completed work orders, and expiring insurance.
Certain events are treated as high priority across the system: portal payments, failed payments, contracts signed or declined, subcontractor incidents, and no-shows.
§Notifications on a single customer
Each customer's NOTIFICATIONS tab shows just the notifications about that customer — colored dot, KIND chip, title, and relative time, with unread items emphasized. MARK ALL READ clears them for that customer only.
LOCKED ON will keep arriving; it is locked for a reason.