Alerts and sounds
Turn on alerts that reach you when Laureo is closed, check that they work on each device, pause them, turn them off, unblock them in your browser, turn on sounds for new email and team chat, and know exactly what they can and cannot do
An alert is the pop-up your computer or phone shows outside Laureo: a banner in the corner of a desktop, a notice on an iPhone lock screen. It is the only thing Laureo has that can reach you when the tab is in the background or the app is closed altogether. Everything else, the bell count and the notifications inbox, needs you to come and look.
Alerts are a separate decision from the bell. Each event has its own Bell and Alert switch, and they are independent: to stop an event's alert, untick Alert. Unticking Bell alone leaves the alert on. New email and Team Chat alert without ever appearing in the bell, because they keep their own counters.
Go to Settings > My preferences > Notifications. The first card is This device, and it tells you where that device stands: Alerts are off for this device. Press Turn on alerts and your browser asks for permission. Say yes and the card changes to Alerts are on for this device.
On your FIRST device, Laureo also switches on a starting set of events for you, so alerts are useful straight away:
- New email
- Cold email replies
- Team chat
- Mentions and assignments
- Approvals
- Meetings starting
Turned on from this page, there is no dialog: the same starting set simply appears already ticked in the Alert column of What reaches you, further down the same page, which has a switch for every event Laureo can tell you about. Untick anything you would rather not hear about and press Save preferences. Turned on from the invitation card instead, a short dialog lists the set, described below.
On a second or third device nothing new is switched on, because your choices already exist and re-asking would invite you to undo them. This page simply says Alerts are on for this device. and the invitation card closes without a word.
If your browser already allowed Laureo's alerts before you pressed the button, it shows no prompt, because there is nothing left to ask. This page and the home page row then say so, for example Google Chrome already allows Laureo's alerts, so it did not ask again.
If Laureo could not save the starting set on your first device (a dropped connection, or a second tab saving at the same moment), it says so rather than leaving you waiting for alerts that will not come. This page says 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. The invitation card says Alerts are on for this device. Choose what you hear about in Settings → Notifications. Either way alerts are on, and the Alert column is where you pick what they are for.
The setup checklist on your home page has an alerts row that says where your devices stand. With alerts on here it reads Alerts on and names the devices that have them, for example iPhone, this Mac. With alerts on elsewhere but not here it reads Alerts on for your other devices with Turn on here, and with none on anywhere, Turn on alerts. Where this device can be turned on with one click, pressing the row turns alerts on right there and it reads Turning on… while your browser asks. If nothing has happened after twenty seconds it says why: Waiting for your browser (its prompt is still open, near the address bar) or Couldn't turn on alerts, and pressing it again tries again. If the browser's question comes back unanswered, the row says where it waits. In Google Chrome, for example: Google Chrome did not show its question. Look for the bell icon at the right end of the address bar, click it, then Allow. Settings and the invitation card say the same. If Google's notification service has refused this device, the row reads Alerts stopped on this Mac (or whichever device you are on) with Turn on again, which sets alerts up afresh right there. On an iPhone in Safari the row takes you to the page that explains what to do instead. In a browser that blocks alerts it reads Alerts are blocked in this browser with See the steps in Settings, and takes you to the steps that unblock them.
The row also tells you when this device's alerts need attention. If they need a quick update it reads Alerts on this Mac need an update (or whichever device you are on) with Update, the same action as in Settings, described in When alerts need a quick update. If this device may not be showing alerts it reads Alerts may not be showing on this Mac with Check it in Settings, which opens the check described in Check alerts on this device. Once a day at most, the home page can also open a short dialog when one of your devices has had alerts sent and none confirmed, with Check alerts and Not now.
You may meet a small card headed Get alerts on this Mac (or this PC, or this device), with the line New email, chat and mentions, even when Laureo is closed. Turn them off any time from the bell. If Laureo already knows that alerts are on for another of your devices, the line says so instead, for example Alerts are on for your iPhone. Turn them on for this Mac too?
Turn on turns alerts on for this device, just as the settings button does. If this browser already allows Laureo's alerts, it turns them on with no browser question at all. Not now sets the card aside for seven days. Don't ask on this device ends it for good on this browser. If it comes back, it offers Turn on and No thanks, and No thanks ends it for good on this browser. While your browser asks, Turn on reads Turning on… and the card's other buttons wait, so a second tap does not ask twice. If the question is still open after a few seconds, the card says where it is: Your browser is asking near the address bar. Choose Allow. Google Chrome sometimes shows that question only as a small bell icon at the right end of the address bar.
On a Mac or a Windows PC, the card then sends one test alert and asks Did you see the test alert? Yes closes it. No opens the steps for your computer's own notification settings, because macOS and Windows can hide alerts your browser allows. The steps come with Open System Settings (Open Settings on Windows) and a link to Settings → Notifications. If the test could not be confirmed, the card says Alerts are on, but the test alert didn't show here. Check this device in Settings → Notifications. A phone gets no test.
On your first device, the card's Turn on is followed by a short dialog headed Alerts are on. It lists the starting set above, every item ticked, so you can untick anything you would rather not hear about before you press Done. Your unticks are saved as the dialog closes, however you close it. If that save does not land, Laureo tells you rather than letting those alerts carry on unexplained: Couldn't save that change. Adjust it in Settings → Notifications. Every choice in the dialog is a normal setting you can change later in the Alert column.
Your browser keeps its alert permission for each browser on each computer or phone. A new laptop, a new browser and a new browser profile each start with nothing answered, so Laureo asks on each one separately. The card appears after you sign in there, a few seconds after the first page opens, once your workspace is set up. On an iPhone or iPad it appears in the Home Screen app, never in Safari, where the install card comes first.
Laureo asks in a browser that has never answered its alert question, and in one that already allows Laureo's alerts but has none on for you. It does not ask where your alerts are already on, where the browser blocks them, or where you turned this device off yourself.
On each browser the card appears at most twice. After Not now it waits at least seven days. Don't ask on this device, No thanks or a block in the browser ends it on that browser only: your other devices are still asked. You never see two invitation cards in one sitting. On an iPhone or iPad, a card the app closed before you answered it (iOS reloads an app it has put in the background) does not start the seven-day wait.
To turn alerts on later, open the bell. When this device is off, the top of the panel says Alerts are off on this Mac (or whichever device you are on) with Turn on. When the browser blocks them it says Blocked in this browser with How to fix, which opens the steps in Settings. Settings > My preferences > Notifications and the alerts row on your home page work too.
Every new email alerts, one notice per conversation, and clicking it takes you to the thing itself.
The first words say what it is
An email alert starts with the word Email and then who sent it, such as Email · Jordan Lee, with the subject on the line below. A Team Chat alert starts the same way, such as Team Chat · Sam Ortiz, and names the conversation too when it is a group. An alert from the AI assistant starts with the word Assistant, such as Assistant · Plan completed. Every other alert already starts with what it is, such as Cold reply: interested, Task assigned or Starting soon. On an iPhone or iPad an alert always shows Laureo's own icon, so these words are what tell you what arrived. The line reading from Laureo under every alert's title there comes from iOS itself: Apple adds it to alerts from every Home Screen web app, and it can't be turned off. On Android and on a computer, an email, Team Chat or cold reply alert also shows a picture of its kind: an envelope, a speech bubble or a reply arrow. With Show sender and preview in alerts off, an alert shows only its kind, such as New email.
Every new email alerts, one notice per conversation
Like an email app, Laureo alerts you for every new email that lands in your inbox, not only the first one in a conversation. In Team Chat, too, every message alerts you. The alerts for one conversation fold into one notice that updates as each message arrives and shows the newest one, so a busy thread leaves one notice, not thirty. The sound plays at most once every two minutes for that conversation, both in the app and on your device. A different conversation still makes its own sound. Some phones, iPhone in particular, may still play their own sound when an alert updates, because the phone decides that, not Laureo. The test alert from Check alerts on this device is never held back this way.
Which emails alert
New email alerts when it arrives unread in the inbox of your own connected mailbox and its category is one you have ticked. The category is the tab your inbox shows the email in. Like Gmail, only Primary is ticked to start with; the other tabs stay quiet until you tick them. Gmail's default tabs are Promotions and Social, so mail Gmail marks as Updates or Forums shows in Primary and alerts as Primary. A tab you turn on under Inbox tabs in the email settings gets its own box, and a tab that is off has no box. Outlook follows its Focused inbox: Focused mail counts as Primary and Other as Updates, so Other stays quiet unless you tick Updates. Choose them under Which emails alert on the New email row in Settings > My preferences > Notifications, or in the Notifications & badge section of the email settings you open from your inbox. Both places save the same choice.
Mail you send to yourself alerts when it lands in your inbox, a reminder you scheduled included; switch Mail you send yourself off to stop that. Newsletters and automated notices alert like any other mail in a category you ticked; switch Skip newsletters and automated mail on to keep them quiet everywhere. Each email alerts once, even if it is marked unread again later. Mail that lands in Junk, Archive or Deleted Items, or that a filter moved past your inbox, never alerts. A reply to one of your cold sequences lands in the mailbox the sequence sent from, not in your own inbox, so it never alerts as a new email: it alerts as a cold reply, described below, and only if that cold reply row has Alert ticked.
Old mail never alerts, and quiet hours delay the alert
Email that is more than a day old when Laureo first sees it, such as the mail brought in when you first connect a mailbox, is added to your inbox and the Email count without an alert. Email that arrives during quiet hours alerts when they end instead, within about 15 minutes of the end of the window, and the held emails of one conversation send one alert, for the newest of them. Each email still has its own row in your inbox. An email you have already read by then sends no alert.
A cold reply alerts once
A reply to one of your cold sequences is one notification, sent once Laureo has read what the reply means. Its title says so, such as Cold reply: interested or Cold reply: not interested, and the line under it shows who wrote and the subject. If reading it takes longer than about 20 seconds, it arrives as just Cold reply and nothing follows later. Like any event, it alerts only if its row in What reaches you has Alert ticked, and with Show sender and preview in alerts off the alert says only Cold reply: not what the reply means, who wrote it or its subject. A reply that reaches two of your sending mailboxes, such as a reply to all, is still one notification. A cold reply that is more than three days old when Laureo matches it to your sequence, such as an old reply read again when a mailbox reconnects, sends no notification.
Clicking it opens the item
Click or tap an alert and Laureo comes to the front in the window you already had open, rather than opening a second one, and takes you to the message, mention or approval it was about. Arriving there marks it read. An email alert opens that email at once, showing it loading while the rest of your inbox fills in behind it, and a cold reply alert opens that reply. On an iPhone or iPad, Laureo may show the page you last had open for a moment while it wakes up, then moves to the item without reloading.
Nothing pops up for what you already have open
An alert still pops up while a Laureo window is in front. The one exception is an alert about the very thing open in that window: the email conversation you are reading in your inbox, or the Team Chat conversation you are in. You are already looking at it, so no pop-up appears. Anything else still pops up: a deal, a task, a different conversation, or the same one in a window sitting behind another app. Safari on a Mac, the Dock app added from Safari, iPhone and iPad show every alert even then, which is Apple's rule rather than ours.
Alerts you dealt with elsewhere clear themselves
Read something on your phone and the alert sitting on your laptop is cleared straight away if a Laureo window is showing there. Otherwise it is cleared when Laureo next loads there with nothing left unread, so while something else is still unread it can stay until you close it. Team Chat alerts clear only on the device where you read the conversation.
Once a device is on, a Check alerts on this device button appears beside it. It sends a test alert to the device in front of you and follows it step by step, one line per step, so you see exactly where it stops and what to do about it. A Laureo window in front does not hold the test alert back, and quiet hours do not hold it either. A pause does: the card then says Alerts are paused, so the test was held. Resume alerts and try again. Before it sends anything, the check makes sure this browser still has alerts on, the server still lists this device, and its alert setup is up to date, and it stops at the first thing that is not, with the button that fixes it.
| Field | Description |
|---|---|
| Sent | The notification service of your browser's maker took the test, for example: Sent to Google's notification service. It is Apple's on an iPhone, an iPad or Safari, and Mozilla's in Firefox. |
| Reached | The device got it, for example: Reached this browser in 2 s. If nothing arrives within 15 seconds the card says so, for example: Google's notification service took the test, but this browser didn't get it. with Quit and reopen Google Chrome, then check again. Still nothing? Press Turn on again. An arrival later than that, up to a minute, still moves the check on. |
| Shown | The browser passed the alert to your system, for example: Google Chrome passed the alert to macOS. On an iPhone it says Laureo passed the alert to iOS. If it could not, the card says This browser got the test but couldn't show it. Reload the page and check again. |
| Did you see the test alert? | Only you can answer this, so the check asks, with Yes and No. Yes ends it with Alerts work on this device. No opens the steps for your device, described below. Your answer is kept with the device, so Your devices can say later that this device was hiding alerts. |
When you answer No, a dialog lists the steps for the device you are using. On a Mac it also has an Open System Settings button, and on a Windows PC an Open Settings button, which open the notifications page there; the steps are always printed, button or not. Check again closes the dialog and runs the check once more. In the Laureo app added from Chrome or Edge on a computer, the steps still name the browser, because the system lists those alerts under it; only the Home Screen app on a phone and a Safari web app in the Dock appear as Laureo. The steps, with Google Chrome as the example browser:
macOS may be hiding Google Chrome's alerts
- Open System Settings, then Notifications, then Google Chrome.
- Turn on Allow notifications. Set the alert style to Banners or Alerts, not None.
- If you also see Google Chrome Helper (Alerts), do the same there. Urgent alerts use it.
- Turn off Focus in Control Center, or add Google Chrome to the apps that Focus allows.
- If you share or mirror your screen, turn on "Allow notifications when mirroring or sharing the display".
- Still nothing? Clear the Google Chrome item from Notification Center, then check again.
- Still nothing? Quit and reopen Google Chrome, then check again. Quitting Google Chrome clears all its old notifications on this Mac.
Google Chrome hands every alert to macOS, whichever app is in front, so you never need to switch apps to see one. macOS lists Google Chrome Helper (Alerts) as a separate app: urgent alerts, the ones that stay on screen until you close them, go through it, and it can be off while Google Chrome is on.
Windows may be hiding Google Chrome's alerts
- Open Settings, then System, then Notifications.
- Turn on notifications for Google Chrome.
- Check that Do not disturb is off.
- Come back to Laureo and check again.
Your iPhone may be hiding Laureo's alerts
- Open the Settings app, then Notifications, then Laureo.
- Turn on Allow Notifications and choose Banners.
- Check that Focus is off and that Scheduled Summary does not hold Laureo.
- Come back to Laureo and check again.
An iPad gets the same steps under its own name.
Your phone may be hiding Google Chrome's alerts (Android, in a browser tab)
- Open your phone's Settings, then Apps, then Google Chrome, then Notifications, and allow this site.
- Check that Do Not Disturb is off.
- Come back to Laureo and check again.
Your phone may be hiding Laureo's alerts (the Home Screen app on Android)
- Open your phone's Settings, then Apps, then Laureo, then Notifications, and allow them.
- Check that Do Not Disturb is off.
- Come back to Laureo and check again.
Your devices keeps each device's last result. A device whose alerts may not be getting through says so in its row: on the device you are using, Alerts may not be showing on this Mac. Check it below., and on another device, Alerts may not be showing there. Open Laureo on that device and check it. Below each row, Details lists the browser, whether its alert setup is up to date, when an alert was last sent, reached it and was shown, the last check and its answer, and the browser permission when Laureo was last opened there.
The part of Laureo that receives alerts keeps running in your browser in the background, and a new version of Laureo can bring a new one. While a Laureo tab stays open, the browser can keep the old one in charge. Laureo now switches to the new one by itself as soon as no open Laureo tab would lose anything. Laureo loads a new version of itself on its own only when you move to another page, or open the installed app after 30 minutes or more away. It never does so over unsaved work, and a page you are reading never reloads on its own. Until the switch can happen, the card says Alerts on this Mac need a quick update. (or whichever device you are on) with one button, Update alerts, and this device's row in Your devices says Update needed. Another device that needs it says Needs an update. Open Laureo on that device and reload.
Most of the time Update alerts finishes with no reload and the check then starts by itself. If another Laureo tab is still open on the old version, the card says Another Laureo tab is still open on the old version. Close it, or reload every tab now. and offers Reload to update alerts, with the note Laureo reloads in every open tab. Save anything you are typing first. After that reload the check starts again by itself. If the browser has not yet fetched the new version, the card says Close every Laureo tab and window, then open Laureo again. The update card that can appear in the corner of any page reads Finish updating alerts while this applies, and it comes back even if you dismissed it.
Four kinds of notice have fixed switches, so you cannot turn them off: security notices about your account, a file of yours being blocked by our malware scan, a scheduled deletion of an account or of the whole workspace, which goes to the workspace admins, and a payment hold notice, which goes to the billing admins. The first three reach the bell and your email, and they alert every device you have turned alerts on for. A payment hold notice reaches the bell and alerts your devices, but it sends no notice email, because the billing email about the failed payment covers it. It comes on the day a payment fails and the day before the workspace locks; the notice that the workspace has locked reaches the bell only. An admin can cancel a scheduled account deletion from Admin > Users until it runs. A workspace deletion can only be cancelled through support, because every member is locked out while it waits, and a deletion that starts at once cannot be cancelled at all. The notice itself says which applies.
"Always on" 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. Their alert is held and sent when quiet hours end too, unless the notice is urgent: most blocked-file notices are, and an urgent notice that does not come through quiet hours is not held, so its alert is not sent later. A scheduled account or workspace deletion is urgent and comes through a quiet window, like an urgent money or deadline notice, because whatever time is left to cancel it is short. A payment hold notice is not urgent: it reaches the bell at once and its alert is held until quiet hours end, which still leaves time to act. All four still respect a pause, exactly like every other alert, and nothing at all comes through a pause.
A pause silences alerts everywhere at once, for a while, and then ends by itself. It is the right control for a meeting or a flight, because nothing is switched off and nothing has to be switched back on. Your bell keeps counting the whole time, so nothing is lost, only quiet.
| Field | Description |
|---|---|
| Pause for 1 hour | Stops alerts on every device for an hour. Notifications still arrive in the app. |
| Pause until tomorrow | Stops alerts on every device until the morning. A pause never runs longer than 24 hours, so a pause you forget about ends on its own. |
| Resume alerts | Ends the pause now. While a pause is running, the card and the bell both say when it will end. |
A pause is saved for your account, so it has to reach Laureo to count. If it does not, the card takes it back rather than showing a pause that is not there, and says Couldn't pause alerts. Check this device's clock and connection, then try again. A resume that does not go through says Couldn't resume alerts. Check your connection and try again. and alerts stay paused until it does.
A nightly window that holds your email and your alerts until it ends, and silences sounds.
Quiet hours are off until you turn them on. To turn them on, switch Enable quiet hours on in Settings > My preferences > Notifications under When and privacy and press Save preferences; the window runs from 22:00 to 07:00 on your own clock until you change its From and To hours there. If you turned quiet hours on before, they stay on. Inside that window, alerts wait for the window to end, email notifications wait too, and no sound plays. The bell keeps counting, so you see everything when you come back.
Alerts are held, not dropped. Every alert you have switched on that arrives during the window is sent when quiet hours end, within about 15 minutes of the end of the window: an @mention, an assignment, an approval, a cold reply, a security notice, new email and team chat alike. Held emails of one conversation send one alert, for the newest of them, and each email keeps its own row. Team chat is held per conversation, and its alerts replace each other on your device, so each conversation leaves one. Nothing is sent for something you have already read before the window ends, and if your alerts are paused when it ends, the pause still applies.
One alert is dropped instead of held: a reminder for a meeting that has already started by the time quiet hours end. Its bell row stays. If you end quiet hours early, or switch them off, the held alerts go out at the next send, within about 15 minutes; if you move the end later, they wait for the new end.
There is one exception, and it is narrow on purpose: urgent money and deadline notices still come through, by email and as an alert. A customer's payment that failed (Payment failed, which includes an autopay that could not collect), a failed payment for your Laureo subscription, a dispute with a deadline, a support commitment that has been breached, a scheduled account or workspace deletion. The page says so on the switch itself: Hold 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. Not every payment notice is on that list: Recurring payment failed, Payout failed, Stripe disconnected and AI Customer Support Agent paused send no alert during quiet hours, like any other notice. Payout failed and Stripe disconnected are urgent notices, and an urgent notice that does not come through is not held for the end of the window either: the bell keeps it.
By default an alert names who it is from and shows a little of what it says. If you would rather that did not appear on a lock screen in front of other people, turn off Show sender and preview in alerts, in the same When and privacy section. The row explains what you get instead: Off shows only the kind of alert, so nothing readable lands on a lock screen. You still learn that something arrived and what kind of thing it was; you just read it in Laureo.
Laureo can play a short sound when new email or a team chat message arrives. It takes two switches in Settings > My preferences > Notifications, and both start off. First turn on Sounds under When and privacy; it saves itself. Then, under What reaches you, switch on Sound on the New email row, the New message row or both, and press Save preferences. A sound plays only when both are on. Two buttons beside Sounds, Hear email and Hear chat, play a sample; they work whether the switch is on or off, so you can hear a cue before deciding.
Sounds cover new email and team chat only; no other event has a Sound switch. A sound needs a Laureo tab open and on screen: if every tab is in the background, the alert is what reaches you, not the sound. When several Laureo tabs are open only one plays, though two separate windows side by side can occasionally both play it. A busy conversation or email thread sounds at most once every two minutes, however many messages arrive. Nothing sounds during quiet hours. A new message in the conversation you are already reading can still play its sound. The reverse can happen in Team Chat: if you open a conversation from an alert or a link and then switch to another one, or go back to the list on a phone, new messages in the first conversation play no sound until you leave Team Chat. Its unread count in the list still updates.
| Field | Description |
|---|---|
| Turn off on this device | On the This device card, and in the bell menu. Affects only the device you are using; your other devices carry on. Turning it back on later is the same one button, or Turn on in the bell. The invitation card does not offer itself again on a device you turned off. |
| Remove, in Your devices | The card lists your devices, each with a line saying what is true of it now: when it last showed an alert (Last alert shown 3m ago, or No alert shown yet), Signed out there. No alerts until someone signs in on it again. for a browser someone signed out of, or Stopped: Google's notification service refused this device. for one Google turned away, which offers Turn on again on the device itself. The one you are on is marked This device and its control says Turn off; every other row says Remove, so you cannot cut off the browser in front of you by mistake. Remove names the device that went: "<device> will not get alerts any more." Turn off on the This device row confirms "Alerts are off for this device." A device you removed from somewhere else reads Alerts are off for this device. the next time Laureo loads on it and offers Turn on alerts, so removing a device you still use is undone there with one click. |
| The Alert column in What reaches you | Keeps alerts on but narrows them: untick the events you would rather only meet in the bell. This is the control to reach for when alerts are useful but too frequent. |
Laureo has to be on your Home Screen first
An iPhone or iPad will not let a website alert you until that site has been added to the Home Screen. Until it is, the card says Add Laureo to your Home Screen to get alerts on this iPhone or iPad. and offers How to add Laureo, which is the short guide in Install App. Its last step is the one that matters: Open Laureo from the new icon, sign in, and tap Turn on alerts. Open it from the icon rather than from Safari, and turn alerts on there.
A long gap can cost you the first alert back
If you do not open Laureo on an iPhone for several weeks, iOS quietly drops its registration. Laureo repairs that the next time you open the app, so nothing needs doing by hand, but the repair happens on open. The practical effect is that the first alert after a long break can be missed. Opening Laureo once is enough to put it right.
No buttons and no pictures
Alerts on iPhone and iPad are text only. The action buttons and images that appear on a desktop alert are not available there, so tapping the alert itself is the whole interaction.
If alerts were refused in this browser at some point, the card says This browser is blocking alerts. and offers no Turn on button, because pressing one would do nothing: a browser records the refusal and no page is allowed to ask again. Only your device's own settings can undo it, so the card prints the steps for the device and browser you are actually using, under a heading that says where the switch lives. In a browser tab that is Allow alerts in followed by the browser's name, and the steps start at the address bar. Safari on a Mac is the exception: its heading is Allow alerts in Safari on a Mac and its steps start at the Safari menu. The installed app has no address bar, so its steps point at the app's own settings instead: Allow alerts in your phone's Settings for the Home Screen app on Android, Allow alerts in App info for a Chrome or Edge app window on a computer, and Allow alerts in System Settings for a Safari web app in the Mac's Dock. On an iPhone or iPad it is always Allow alerts in the Settings app.
iPhone and iPad
- Open the Settings app, then Notifications, then Laureo.
- Turn on Allow Notifications.
- Open Laureo again from its Home Screen icon, then turn alerts on again.
Alerts on an iPhone or iPad only exist in the Laureo app on your Home Screen, and its permission lives in the Settings app rather than in any browser menu.
Chrome, and other Chromium browsers
- Select the icon at the left of the address bar (a lock, a slider, or Site information).
- Find Notifications in the list and set it to Allow.
- Reload this page, then turn alerts on again.
Edge
- Select the lock icon at the left of the address bar.
- Select Permissions for this site.
- Set Notifications to Allow, then reload this page.
Firefox on a computer
- Select the lock icon at the left of the address bar.
- Select Connection secure, then More information, then Permissions.
- Clear the Blocked setting for Send Notifications, then reload this page.
Firefox on an Android phone
- Tap the lock icon at the left of the address bar.
- Set Notification to Allowed, then reload this page.
Safari on a Mac
- Open the Safari menu, then Settings, then Websites, then Notifications.
- Find app.laureo.io in the list and set it to Allow.
- Come back to this tab and reload the page.
The card names the address you are actually on in step 2, so if you open Laureo at a different address, look for that one in the list.
Apart from iPhone and iPad, the steps above are for Laureo in a browser tab. Opened from its Home Screen, Dock or app icon, Laureo runs in a window of its own with no address bar, and the card prints these instead:
The Home Screen app on Android
- Open your phone's Settings, then Apps, then Laureo, then Notifications, and allow them.
- Open Laureo again from its Home Screen icon, then turn alerts on again.
A Chrome or Edge app window on a computer
- Open the app menu at the top of the window, then App info, and set Notifications to Allow.
- Close the Laureo window, open it again, then turn alerts on again.
A Safari web app in the Mac's Dock
- Open System Settings, then Notifications, then Laureo, and allow notifications.
- Close the Laureo window, open it again from the Dock, then turn alerts on again.
An app added from Firefox
It keeps its permission in Firefox itself, under the heading Allow alerts in Firefox, so its steps start with Open app.laureo.io in a Firefox tab. and then follow that tab's Firefox steps above. On an Android phone, where Firefox adds Laureo to the Home Screen from its own menu, they are Tap the lock icon at the left of the address bar. and Set Notification to Allowed, then reload this page.
One line a day, in the bell and in your daily digest email.
When an action from one of your AI agents has waited for your approval for more than 4 hours, Laureo adds one line for you, such as 3 agent actions wait for your approval, with the names of the agents that are waiting, such as From Lead Follow-Up and Deal Follow-Up. It never names a record, an email subject or a sender. Click it to open your approvals. The line goes to the person who created the agent, or to the person the agent runs as when the creator is not known. If your role can approve agent actions, you decide them there. If it cannot, the approvals page says so, and only someone whose role can approve can decide them.
You get at most one line a day, and only on a day when something has waited that long. It reaches your bell and your daily digest email, sent at your Digest delivery time. It sends no alert unless you tick Alert on its row, Approvals waiting, in the AI Agents group of Settings > My preferences > Notifications. To stop the email, set that row's email to Off; the bell line stays.
- Alerts are best effort. They travel through your browser maker's delivery service. Laureo hears back when a device receives and shows one, but an alert that never arrives sends nothing back, and nothing tells Laureo whether you looked. Almost all of them do arrive. Treat the bell, not the alert, as the record of what happened.
- An iPhone can drop its registration after weeks without opening the app, so the first alert after a long break can be missed. Laureo repairs it when you next open the app.
- Laureo cannot see your Do Not Disturb, or any other setting on your device that hides an alert. Use quiet hours or a pause instead, and Check alerts on this device when you are not sure alerts are showing.
- A blocked browser cannot be unblocked from this page, only from the browser's own site settings in a tab, from the installed app's own settings (your phone's Settings on Android, App info in an app window on a computer, System Settings for a Mac Dock app), or on an iPhone or iPad from the Settings app.
- Sometimes it is simply unavailable. The card says Alerts are not available on this device right now. and explains that 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 offers Try again, which is worth pressing: about half the time this is a temporary connection problem rather than a browser limit, and the two look identical from here.
A notification profile can tick Alert for the events a team should hear about, so a new joiner does not have to work out a sensible set for themselves. The admin screen states the limit plainly: These reach members when you assign this profile to them, unless they changed their own settings. Alerts arrive only after a member turns alerts on for one of their own devices. Permission to grant a device is the person's to give, and no profile can give it for them. To put members on a profile, use Assign on its row in Admin > Notification Profiles; see Notification Profiles.
A profile sets no time zone. The page says so where the picker used to be: Digest times and quiet hours run on each member's own profile time zone, not a zone set here. Its quiet-hours controls are labelled Quiet from and Quiet until. Managing notification profiles needs the same permission as managing users.