Where to find it
Everything here lives in Settings → Notifications. The personal preferences are open to everyone; the organisation override section shows only for admins.
Start here
The 60-second version
Open Settings → Notifications. You’ll see a short table of notification types, each with two switches: In-app and Email. Flip the ones you want; changes save as you go.
NotificationIn-appEmail
Channel disconnection alert
When a connected channel (e.g. WhatsApp) disconnects.
Lead assignmentNew
When a teammate assigns you to a lead.
Contact assignmentNew
When a teammate assigns you to a contact.
What you can be notified about
There are three notification types today. New ones get added to the same table over time, marked New when they appear.
Channel disconnection alert
A connected channel — WhatsApp, Telegram and so on — dropped, so nothing can reach your Inbox until it’s reconnected. The one you don’t want to miss.
Lead assignment
A teammate made you the owner of a lead — the deal is now yours to drive. A lead has one owner at a time, so this is a clear hand-off of responsibility.
Contact assignment
A teammate added you as a collaborator on a contact — often by @mentioning you in an internal note, which also gives you access to that contact. A contact can have several people assigned at once.
Lead vs contact — what’s the difference?
Lead assignment is about ownership — one person is made responsible for a deal in a pipeline. Contact assignment is about collaboration — you’ve been added to a person’s record so you can help work it, and a contact can have several people assigned. The most common way contact assignment happens is being @mentioned in an internal note, which assigns you and grants access in one step.
In-app vs email
Each type can reach you on two channels, and you control them separately:
- In-app — a notification in Exabloom’s bell while you’re working.
- Email — an email to your inbox, useful for alerts you need even when you’re not in the app.
Tip
A common setup: keep in-app on for everything, and reserve email for the alerts you can’t afford to miss — like a channel disconnection.
Admins only
Admin: enforce or block
Sometimes a notification is too important to leave to personal choice. On the same page, admins get an Organisation notification settings section to set a policy per type and channel.
Organisation notification settings
Channel disconnection alert · Email
No override
Users control their own preference.
Force on
Everyone receives it, regardless.
Force off
Block it for everyone, regardless.
Applies to all users — or pick specific people.
- No override — the default. Everyone keeps their own preference.
- Force on — everyone receives it, even if they’d turned it off.
- Force off — block it for everyone, even if they’d turned it on.
- Either force can apply to all users or to selected people — pick names and the rest keep their own choice.
What forced users see
When you force a setting, the affected toggle on each person’s page is locked with a note that an admin enforced it. Set the policy back to No override to hand control back.
Good to know & pitfalls
- Everything starts ON. Notifications are opt-out — you’ll receive each type until you turn it off, so new teammates are covered by default.
- In-app and email are independent. Turn email off but keep the in-app bell on (or the reverse) for any type — they’re two separate switches.
- A locked toggle is your admin’s doing. If a switch is greyed out with an amber note, an admin has enforced that setting for the organisation and you can’t change it yourself.
- The disconnection alert is the one to keep. It’s how you find out customers can’t reach you. Leave it on unless someone else on the team owns reconnecting channels.
- Your preference is per person. Changing your toggles only affects what you receive — not your teammates. Org-wide changes are the admin section’s job.
Keep learning
Need a hand?
Our Singapore-based team is one message away — happy to help you get set up.