Help Center

Docs

Alerts

Turn on alerts that reach you when Laureo is closed, pause them, turn them off, unblock them in your browser, and know exactly what they can and cannot do

What an alert is

The one thing that reaches you when Laureo is not open.

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.

Off until you turn them on, on each device
Alerts start off, and you turn them on once per device: your work laptop, your phone and your home computer are three separate decisions. Once a device is on, alerts go to every device you have turned on, not just the one you are using.

Turning alerts on

One button per device, and a starting set of events on the first.

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
  • 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 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.

Laureo never triggers the browser prompt on its own
The browser permission box only ever appears after you press one of our own buttons. Laureo does not open it when you arrive, and it does not open it from a banner you did not click. That matters, because a browser permanently blocks a site that asks and is refused, and no page can ask a second time.

If you were offered alerts on a card

Get alerts for new email, chat and mentions.

You may meet a small card headed Get alerts for new email, chat and mentions. Turn on turns alerts on for this device, just as the settings button does. Not now sets it aside and you may see it once more on a later visit. Don't ask again ends it for good on that kind of device. If it comes back, it offers Turn on and No thanks, and No thanks ends it for good on that kind of device. The card appears at most twice per device type, at least fourteen days apart, and you will never see two invitation cards in one sitting.

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.

What an alert looks like, and what it does

One per conversation, and clicking it takes you to the thing itself.

One per conversation, not one per message

In Team Chat every message alerts you, but the alerts collapse onto one another so a busy conversation leaves one notice, not thirty. Email is quieter still: one alert per thread while it is unread, so a long back-and-forth does not alert you twice.

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.

Nothing pops up while you are already here

Except on an iPhone, an iPad, or in Safari on a Mac (including Laureo added to the Dock from Safari), a focused Laureo window means no pop-up: you are looking at the thing it would have told you about. That is every other browser, on a computer or an Android phone: Chrome, Edge and Firefox, and Samsung Internet and Opera as well, and Laureo installed from Chrome or Edge too. Safari on a Mac, the Dock app added from Safari, iPhone and iPad always show them, 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.

Send yourself a test alert

Prove it works on the device you are holding.

Once a device is on, a Send a test alert button appears beside it. Press it and Laureo replies: Test alert sent. Except on an iPhone, an iPad, or in Safari on a Mac (including Laureo added to the Dock from Safari), a Laureo window in front hides the pop-up: switch to another app or tab, or check another device. That is worth reading rather than skipping, because everywhere else a test sent while you are looking at Laureo is deliberately not shown. Safari on a Mac, the Dock app added from Safari, iPhone and iPad show it anyway.

Three things you cannot switch off

Alert, always on.

Three 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, and a scheduled deletion of an account or of the whole workspace, which goes to the workspace admins. They reach the bell and your email, and they alert every device you have turned alerts on for. 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, and no alert is sent for them 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. All three still respect a pause, exactly like every other alert, and nothing at all comes through a pause.

Pausing alerts

Quiet on every device, without turning anything off.

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.

FieldDescription
Pause for 1 hourStops alerts on every device for an hour. Notifications still arrive in the app.
Pause until tomorrowStops 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 alertsEnds 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.

The same switches live on the bell
You do not have to go to settings to go quiet. Open the notification bell and, if this device has alerts on, a strip at the top of the panel says Alerts on for this device with an Alerts menu beside it holding On, Pause for 1 hour, Pause until tomorrow, Turn off on this device and Notification settings. The bell is where you go when an alert has just annoyed you, so the way out is there.

Quiet hours

A nightly window that holds your email and silences your alerts.

Quiet hours are on from the start, from 22:00 to 07:00 on your own clock. Inside that window, Laureo holds your email notifications until the window ends and sends no alerts at all: an alert for something that happened overnight is not sent later, in the morning or ever. The bell keeps counting, so you see everything when you come back. To move the window, change its From and To hours in Settings > My preferences > Notifications under When and privacy; to have alerts around the clock, switch Enable quiet hours off there and press Save preferences.

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 until quiet hours end, and send no alerts during them. 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.

Quiet hours run on one time zone, and the page names which
Quiet hours and your digest times run on a single zone, and the notifications page states which one it found and what time it is there right now. It is honest about where the zone came from, because that decides what you should do about it. Laureo looks in this order and uses the first it finds: your profile time zone if you have set one; 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 if none of those is set, the page says UTC, because no time zone is set for you or for this workspace. The link beside it reads Change it in Profile when the zone is already yours, and Set your own in Profile when it is not.
Your digests may arrive at a different hour than they used to
Because digests now follow that same profile time zone, a daily or weekly 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, so if that was not the zone you work in, your digest will move to the hour you actually chose. Nothing is lost; the time is simply the one the setting always claimed.
Why quiet hours are in Laureo and not left to your computer
A website cannot see whether your computer or phone is in Do Not Disturb, so Laureo cannot follow it. Quiet hours exist so there is a setting that does work.

Keeping content off your lock screen

Show sender and preview in alerts.

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.

Turning alerts off

Per device, and per event.

FieldDescription
Turn off on this deviceOn 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.
Remove, in Devices getting alertsThe card lists every device currently getting alerts, with when each was last used. 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 youKeeps 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.
Sign out yourself on a shared computer
Signing out removes this device's alerts. An automatic sign-out after a period of inactivity does not, so on a shared or borrowed computer, sign out yourself or press Turn off on this device before you leave it. After signing out, sign back in and turn alerts on again to restore them.

iPhone and iPad

Two things Apple requires that no website can work around.

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 two-step guide in Install App. Add it, open Laureo from the new 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 your browser is blocking alerts

This browser is blocking alerts.

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

  1. Open the Settings app, then Notifications, then Laureo.
  2. Turn on Allow Notifications.
  3. 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

  1. Select the icon at the left of the address bar (a lock, a slider, or Site information).
  2. Find Notifications in the list and set it to Allow.
  3. Reload this page, then turn alerts on again.

Edge

  1. Select the lock icon at the left of the address bar.
  2. Select Permissions for this site.
  3. Set Notifications to Allow, then reload this page.

Firefox on a computer

  1. Select the lock icon at the left of the address bar.
  2. Select Connection secure, then More information, then Permissions.
  3. Clear the Blocked setting for Send Notifications, then reload this page.

Firefox on an Android phone

  1. Tap the lock icon at the left of the address bar.
  2. Set Notification to Allowed, then reload this page.

Safari on a Mac

  1. Open the Safari menu, then Settings, then Websites, then Notifications.
  2. Find app.laureo.io in the list and set it to Allow.
  3. 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

  1. Open your phone's Settings, then Apps, then Laureo, then Notifications, and allow them.
  2. Open Laureo again from its Home Screen icon, then turn alerts on again.

A Chrome or Edge app window on a computer

  1. Open the app menu at the top of the window, then App info, and set Notifications to Allow.
  2. Close the Laureo window, open it again, then turn alerts on again.

A Safari web app in the Mac's Dock

  1. Open System Settings, then Notifications, then Laureo, and allow notifications.
  2. 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.

Laureo will not nag you about it
A blocked browser is a decision, and Laureo treats it as one. There is no recurring banner asking you to reconsider. The steps are in settings for the day you want them, and that is all.

What alerts cannot promise

The honest limits, in one place.

  • Alerts are best effort. They travel through your browser maker's delivery service, and there is no receipt that says one arrived. Almost all of them do. 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. Use quiet hours or a pause instead.
  • 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.

For admins

You can suggest alerts, but you cannot turn them on for someone.

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 assigned this profile who have not customised their own notification 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.

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.