Help Center

Docs

Notification Settings

The one page that decides what reaches you: alerts on this device, the bell, alert and email switch for every event, a sound for new email and team chat, digests, quiet hours and alert privacy

Three questions, in order

Control how and when you're notified about activity.

Settings > My preferences > Notifications is laid out as three questions, answered top to bottom:

1. This device

Whether the browser you are sitting at can show you an alert when Laureo is closed. This is a per-device decision, so it is asked first.

2. What reaches you

Which events reach you, and by which route. Every event has its own bell, alert and email switch, and New email and New message also have a sound switch.

3. When and privacy

Digest schedule, quiet hours, and what an alert is allowed to show on a lock screen.

Below those three, the page repeats your Inbox view preferences, which are about how the notifications list looks rather than what reaches you, and so come last. The full triage workspace is the Notifications Inbox at /notifications.

If an admin gave you a starting point

A notification profile sets your baseline, and you can overrule any of it.

If your admin has assigned you a notification profile (for example, Sales Rep Default), a banner at the top of the page names it. The profile is a baseline, not a lock: change any switch and the banner adds You've customized the baseline. An admin can reset you back to the profile, which is the only thing that overwrites your own tuning.

This device

Alerts reach this browser even when Laureo is closed. Turn them on once per device.

The card states where this device stands in one line, and offers only the buttons that make sense for that state:

FieldDescription
Alerts are off for this device.The starting point. Turn on alerts asks your browser for permission. On your first device it also ticks a starting set of events in the Alert column below (new email, cold email replies, team chat, mentions and assignments, approvals, meetings starting), with no dialog, so untick anything you would rather not hear about and save. A later device changes nothing in that column. If the browser's prompt is still open twenty seconds later, the card says Waiting for your browser. Answer its prompt near the address bar.
Alerts are on for this device.Alerts arrive on this device until you turn them off or remove it below. Check alerts on this device and Turn off on this device appear beside it. The check follows a test alert from Sent to Reached to shown on screen, then asks whether you saw it, and stops at the first thing in the way with the button that fixes it. If this device needs a quick update first, the card says so and offers Update alerts. If the starting set could not be saved on a first device, the card says instead: Alerts are on for this device. We couldn't pick a starting set of events for you, so choose what alerts you in the list below. If your browser already allowed Laureo's alerts, it shows no prompt, and the card adds, for example: Google Chrome already allows Laureo's alerts, so it did not ask again.
This browser is blocking alerts.Alerts were refused here at some point and no page is allowed to ask again. The card prints the unblock steps for the browser you are using; there is no Turn on button, because it would do nothing.
Add Laureo to your Home Screen to get alerts on this iPhone or iPad.Apple will not let a website alert you until it has been added to the Home Screen. The card offers How to add Laureo instead of a switch.
Alerts are not available on this device right now.Shown with: This browser may not support alerts, or the app could not reach the alert service. Any other devices you have turned on are unaffected. It is worth pressing Try again, because about half the time this is a temporary connection problem rather than a browser that cannot do it.
Google Chrome did not show its question. Look for the bell icon at the right end of the address bar, click it, then Allow.Shown in Google Chrome on a computer, and under their own names in Microsoft Edge, Opera and Vivaldi, when the browser's question came back unanswered. These browsers can keep the question quiet behind a bell icon in the address bar, and a page cannot tell that from a question you closed. Nothing is blocked: click the bell and choose Allow, or press Turn on alerts again.
You didn't answer the browser's prompt. Press Turn on alerts and choose Allow.The same answer in Safari, Firefox, on a phone or in the installed app. Nothing is blocked, so pressing Turn on alerts asks again. Do not keep closing it: browsers count repeated dismissals and eventually stop asking on their own.
Alerts can be turned on only at app.laureo.io.Shown when Turn on alerts was pressed on a page that is not the Laureo app, such as a preview link. Open app.laureo.io and turn alerts on there.

Underneath, Pause alerts offers Pause for 1 hour and Pause until tomorrow, which silence every device you own at once while the bell keeps counting. Your devices lists each device with when it last showed an alert, or that it was signed out, refused, needs an update or needs a check, with its Details below it and a Remove button (Turn off on the row for the device you are using). All of it, including how to unblock a browser, is covered in Alerts and sounds.

Turning alerts on here is not the same as choosing what alerts
Turning a device on decides where alerts can reach you. Which events alert you is the Alert column in the next section: your first device ticks a starting set there for you, and a later device leaves the column exactly as you set it. The page says so above the grid: Alerts go to every device you have turned on. Tick Alert on the events worth interrupting you for. Before any device is on it says the other half: Alerts start off for every event. Turn alerts on for a device above, then tick the events you want.

What reaches you

Per event: the bell in the app, an alert on your devices, a sound, an email.

Two account-wide switches sit at the top of this section, then the grid.

FieldDescriptionTypeDefault
Auto-watch records I own or am assigned toWhen you become the owner or assignee of a deal, task, company, project, or ticket, you automatically receive notifications for changes. You can unwatch individual records anytime.toggleOn
Show popup for high-priority notificationsWhen enabled, urgent and high-priority notifications surface as a toast in the corner of the screen. The bell badge always updates either way. This is an in-app toast while you are looking at Laureo, which is a different thing from an alert.toggleOn

The columns on every event

A channel that cannot carry an event shows no switch on that row.

FieldDescription
BellWhether the event appears in the bell and in the notifications inbox, and counts towards the unread number.
AlertWhether the event alerts the devices you have turned alerts on for. The switches are disabled until at least one device is on, because nothing could deliver them.
SoundA per-event sound switch. It appears on the two events that keep their own counters, New email and New message, and pairs with the Sounds control in When and privacy. It starts off, and a sound plays only when this switch and Sounds are both on.
EmailWhether the event emails you at all.
Email modeHow it emails. Immediate sends within about two minutes. Digest holds it for your daily or weekly roundup. None turns the email off while keeping the bell. The dropdown is disabled when Email is off.
Email and Team Chat never add to the bell
New email and new team chat messages keep their own counters, on the Email and Team Chat rows in the sidebar, and they never add to the notification bell. The same message is therefore never counted twice. Reading the message clears its hidden twin in the notifications lane, never the other way round, so a glance at the bell can never mark your mail as read. Those rows are marked This one has its own counter in the grid. The split is explained in My Work vs Notifications.
Some rows say Alert · always on
Security notices, a file of yours blocked by our malware scan, and a scheduled deletion of an account or of the whole workspace (sent to the workspace admins; an admin can cancel an account deletion, and a workspace deletion is cancelled through support) carry an Alert · always on label and disabled switches. They always reach the bell and your email, and they alert any device you have turned alerts on for. The payment hold notice, sent to billing admins, is the one exception on email: it always reaches the bell and your alert devices, but it sends no notice email, because the billing email covers it. The day 7 notice, which says the workspace has locked, reaches the bell only. The label is about the switches, not about the clock. Security notices and blocked files do not alert during quiet hours: they reach the bell at once and your email when quiet hours end, and their alert is held for the end too unless the notice is urgent, as most blocked-file notices are. A scheduled account or workspace deletion is urgent and comes through a quiet window, like an urgent money or deadline notice. All four still respect a pause, like every other alert.
Task due soon surfaces in My Work instead
The Task due soon row shows its bell switch disabled with the note Surfaces in My Work instead. Task reminders are work, so they live in the My Work Overdue and Today sections rather than as a separate bell notification. The email control for the row still works if you want the reminder by mail.

Set a whole category's email frequency

One control per category header, instead of opening every row.

Every category header carries an Email frequency control with four options, and it applies to every email-capable event in that category at once.

FieldDescription
Real-timeOne email as soon as each event happens.
DailyBatch them into your daily digest, sent at your Digest delivery time.
WeeklyBatch them into your weekly digest, sent on your Weekly digest day.
OffNo email for this category. The bell is a separate switch and stays as it is.
Custom means you tuned events individually
Change one event so it no longer matches the others and the category control shows Custom with none of the four highlighted. That is not an error, just a mix. Pick any of the four to put the category back in step, or leave it on Custom.
A few events keep their own delivery
The always-on safety events always email immediately and the category control does not change them. A few others are left out on purpose: the new-email event (it cannot email you about email without looping), the trial and subscription billing reminders, which send their own dedicated emails, and the promotion notice, which is emailed only when the Laureo team adds a promotion. You can still tune any of them by hand in its own row.
Typical volume
Each category header carries a small Typical volume caption, such as Daily in an active workspace, A few per week, Occasional or Rare, so you know how noisy a group is before you tune it. It is a rule of thumb, not a promise.

The categories

Related events grouped so you can decide once instead of forty times.

Assignments & Activities

Activity assignments, reminders for upcoming activities, and deal pipeline stage changes.

Mentions & Collaboration

Mentions in notes and comments, updates to records you are watching, and new direct or group messages.

Tasks

Task assignments, comments on tasks assigned to you, due-soon reminders, and completions of tasks you created.

Approvals

Requests for your approval, and responses to your pending approval requests.

Manager & Team

Manager responses and direct nudges from your manager.

System & Operations

Import completions, import rollbacks, export readiness, automated workflow notifications, usage alerts, trial-ending reminders, promotion notices, and meeting transcript and recording linking.

AI Agents

Agent run completions, failed actions, run failures, expiring pending actions, agent paused alerts, Laureo chat ready, and Laureo chat failed notifications.

Tickets & Support

Ticket created, reply received, ticket assigned to you, and ticket resolved.

Goals & Leaderboard

Goal achieved and goal-at-risk alerts for goals you own.

Campaigns & Outreach

Campaign completed and paused, interested replies and unsubscribe requests, test decisions, and cold outreach replies and sequences.

Meetings & Calendar

Meeting invites received and starting-soon reminders, ten minutes before start.

Email

New mail. This row keeps its own counter and carries two extra controls of its own, below.

Security & Files

New device logins and sign-in locations, account access and role changes, files rejected by our antivirus scan, and scheduled or cancelled account deletions. New device logins, blocked files and scheduled deletions cannot be turned off.

Two rows with extra controls

Team chat and email each carry a choice the others do not need.

FieldDescriptionDefault
Messaging notification scopeOn the new-message row. All conversations, or Direct messages only. With DM-only, group chats and channels stop notifying you. Per-conversation mute still applies within whatever you choose here, so a muted DM stays muted.All conversations
Sidebar email badge scopeWhat the Email sidebar number counts: Primary-tab mail only (skipping promotions, social, updates and forums), All unread inbound emails, or Only CRM-matched contacts.Primary-tab mail only

When and privacy

Digest schedule, quiet hours, and what an alert is allowed to show.

FieldDescriptionTypeDefault
Digest delivery timeThe hour your daily digest is sent, and the hour the weekly one is sent on its day.dropdown08:00
Weekly digest dayThe day of the week for the weekly digest.dropdownMonday
Enable quiet hoursHold email and alerts until quiet hours end, and play no sounds during them. Held alerts are sent when they end, one per email thread or chat, and a reminder for a meeting that has already started is dropped. Urgent money and deadline notices still come through, and the bell keeps counting. Every alert you switched on is held, an @mention included, and the held alerts arrive within about 15 minutes of the end of the window: the emails of one conversation as one alert for the newest, and each conversation as one. Nothing is sent for something you have already read. Ending quiet hours early sends the held alerts at the next send; moving the end later holds them to the new end. Off until you switch it on; the window then runs from 22:00 to 07:00 on your own clock.toggleOff
Quiet hours windowA From and a To hour. A window that crosses midnight, such as 22:00 to 07:00, wraps correctly.22:00 to 07:00
Show sender and preview in alertsOff shows only the kind of alert, so nothing readable lands on a lock screen. You still learn something arrived and what kind of thing it was.toggleOn
SoundsPlay a short sound in the app for new email and team chat. A master switch plus two buttons, Hear email and Hear chat, which play a sample so you can hear each cue. The buttons work whether the switch is on or off. This switch alone plays nothing: also switch on Sound on the New email row, the New message row or both in What reaches you, and press Save preferences. Both start off. Sounds cover new email and team chat only, and they follow quiet hours.toggleOff
Quiet hours and digests use one time zone, and the page names it
The page states the zone it is using, what time it is there right now, and where that zone came from, checked in this order: your profile time zone; otherwise the time zone saved here earlier, if an older version of this page still holds one for you; otherwise the workspace time zone; and with none of those, UTC, because no time zone is set for you or for this workspace. The link reads Change it in Profile when the zone is already yours and Set your own in Profile when it is not. The separate time zone picker this page used to carry is gone; it decided nothing for anyone who had a profile zone.
Your digests may now arrive at a different hour
Because digests follow that profile zone, a digest set to 08:00 arrives at 08:00 on your own clock. Until this release, 08:00 meant 08:00 in the zone saved on this page, or UTC if none was saved. If that was not the zone you work in, your digest will move to the hour the setting always claimed.
If your digest time falls inside quiet hours
You can pick a digest time inside your quiet window. Save it and the page notes: Your digest time falls inside quiet hours; the digest will send after quiet hours end. The digest is delayed, not lost. Move either time if you would rather it arrive on the hour.

Saving

One Save bar, and two rows that save themselves.

The delivery form has a single sticky bar with a Save preferences button, which reports Saving… and then All changes saved. If your preferences were changed somewhere else while you were editing, in another tab or on another device, that save is refused so it cannot quietly overwrite the other change, and the page says: These settings changed somewhere else while you were editing. Your changes are still here: press Save preferences again to apply them on top. Your pending changes stay on screen, so do not reload the page, which would throw them away. Press Save preferences again and they are applied on top of the newer settings.

Two rows are deliberately outside that form and save themselves the moment you change them: Show sender and preview in alerts and Sounds. They belong to the same store as your inbox view preferences, so they need no Save.

Manage links jump to the exact row
Every notification email has a manage link in its footer that opens this page scrolled to that event's own row, so you can change how one thing reaches you without hunting for it.