Skip to content

Email settings

51 help pages

Where the service has turned email settings on, Settings → Email is where you choose which emails you get. It is open to every signed-in person, whatever their role. It is the first page in the Settings menu, under the heading Your account. Until the service turns it on, the page is not in the menu and an address that reaches it says Email settings are not available yet. Your choices then stay where they are today: the Email preferences card on the Notifications tab of Profile, and the weekly summary and monthly report checkboxes.

The page opens with "Choose which emails you get. An email marked Also in the dashboard bell still shows there whatever you choose here." Each choice saves as soon as you change it, and a message confirms it or says Could not save this choice. Try again. If the page cannot load, it says Your email settings could not be loaded. Check your connection and try again. Select Try again.

The four groups. Every email belongs to one group. Each group has one switch, a state, and an arrow to show or hide the single emails in it:

  • Critical issues and alerts: security problems, sites that stop sending data or go out of date, certificate problems, a changed site key, deployments that fail or cannot be confirmed, and account security emails such as a new sign-in, a changed password, or the notice that your CLI sign-ins and API tokens have stopped. Turning any of these off needs a confirm step (see below).
  • Recommended emails: useful updates about your sites, reports and support, such as end of life notices, configuration drift, the monthly report and password expiry.
  • Optional emails: good news and summaries, such as Fix confirmed, New release seen, Data arriving again, All quiet this week and Weekly summary.
  • Required emails: sent because you asked for them, or because the law or your account needs them, such as password reset, email verification, data export links and billing emails. They show Always sent with a lock and cannot be turned off.

With Patching, Security scan findings is in Critical issues and alerts too: an email when a security scan of a site's repository finds new serious problems.

A group's state reads On, Off, Custom or Always sent. Custom means some emails in the group differ from the rest. A note can add how many emails are off by default. The group switch turns every email in the group on or off. From Custom, the switch turns the whole group on.

Each email. Open the arrow to see the single emails. A row shows the email's name, a small tag for its area (Website, Reports, Account, Support, Billing or Administration), a short description, and its own switch. A row says Also in the dashboard bell when the same alert also shows in your bell. Those alerts keep showing in the bell whatever you choose here.

Two levels. The page works at two levels:

  • All organisations and your account: your choices for every organisation you belong to, and for emails about your account.
  • Your organisations: one collapsed row for each organisation. The row says Same as above when you have made no separate choice there, or 1 change or N changes when you have. Open it to make choices for that organisation only. They win over the choices above. Select Use the choices above to remove them.

Replace organisation choices? If you change a group at the top level while some organisations have their own choice for that group, a dialog lists them and asks whether to replace them. Replace applies your new choice everywhere. Keep them applies it only where an organisation has no choice of its own.

Pause Recommended and Optional emails. The switch at the top stops both groups in every organisation and keeps your choices, so turning it off brings them back. While it is on, a banner reads Recommended and Optional emails are paused. Critical and Required emails still go.

Turning off a Critical email. Turn off a Critical switch, or the whole group, and the dialog Turn off Critical emails? lists the emails that will stop. An email that also shows in the dashboard bell is marked (still shows in the dashboard bell). If none of the emails reach you today, the dialog says so instead: the choice would still stop them later, for example in an organisation you join. Select Turn off to confirm or Keep them on to leave things as they are. If you are the only person who gets one of these emails in an organisation, the dialog adds a warning: Nobody in will get the email. Think before you confirm, because nobody would be emailed about that problem. Turning a Critical email back on needs no confirm step.

Organisation administrators. The page shows an administrator Nobody in this organisation gets: followed by the Critical emails that no member of that organisation currently receives. It counts the organisation's alert audience and whether members have a verified email address. The same warning shows on Settings → General, with a link to this page. It names emails, never people, and only administrators see it. Each person still chooses their own emails, so an administrator cannot turn another member's emails on. To fix it, ask members to turn the email on, or change Security alert audience: email all members for security alerts.

Email only. This page changes email, not phone alerts. Urgent alerts by SMS and Security alerts by phone stay under Mobile number, and the page does not change them.

What is listed. The page lists only emails you can actually get. Emails for features the service has not turned on, for products your organisation does not have, and for roles you lack are left out. Emails for administrators only, such as certificate problems, a changed site key, the monthly report, the weekly summary and billing emails, show only for organisation administrators. If your role changes, the list changes with it.

Patching emails, such as pull request updates, deployment failures and Autopilot approval requests, carry the Patching tag. They are listed only where your organisation has Patching. Security scan findings is open to every member. Its two administrator-only companions, a security scan that did not finish and no security scan in 30 days, are part of Patching needs attention, which only organisation administrators see.

Links in emails. Where email settings are on, every email Sentinel sends you ends with Choose which emails you get, which opens this page (sign-in needed). Recommended and Optional emails also end with Stop these emails, and your mail app may show an Unsubscribe button for them. Critical and Required emails never have these.

Stop these emails. The link opens a page, Stop these emails?, that names the email. Opening it changes nothing. Select Stop these emails to turn that email off, or Stop all Recommended emails (or Stop all Optional emails) to turn off the whole group. The change applies to the organisation the email was about, or to every organisation for emails about your account. The page then says Done. Emails already sent cannot be recalled, and selecting the button again changes nothing. The mail app's Unsubscribe button stops that one email straight away. Choose all your emails opens this page.

The link needs no sign-in, so anyone you forward the email to could stop that email for you. The page never shows your email address or organisation. A link stops working when you change your email address; an old or broken link says This link isn't valid. Use the link in a recent email, or sign in and use this page.

Other ways in. Email choices can be turned off in the dashboard only. The command line, MCP and personal API tokens cannot turn off a Critical email.

Sessions and signed-in products

The Sessions and devices tab of Profile opens with a Sessions and signed-in products card, followed by Browser extensions and CLI and MCP sign-ins. The card is for any signed-in account and shows only your own data. It has three lists:

  • Signed-in products names each product that is signed in through your TrueCMS account, with its session count, for example "Uptime (2 sessions)". If there are none, the card says No product is signed in through your TrueCMS account.
  • Active sessions shows, for each sign-in, the browser and system, the IP address, when you signed in, how you signed in (for example Password, or Password and authenticator code, Google or GitHub), when the session ends, and the products it reached. Without any, the card says No active sessions.
  • Recent sign-ins shows up to the 10 latest sign-ins with the time, product, method, device and IP address. Already signed in means a product used a session you already had, so you did not enter your password again. Without any, the card says No sign-ins recorded yet.

Where the shared sign-in service is not turned on for your installation, these lists are empty. While loading, the card says Loading…. If it fails, it says Your sessions could not be loaded.; reload the page to try again.

To end every session, select Sign out everywhere. The card then asks you to confirm: Every product signs you out, including this dashboard. You will need to sign in again. Select Sign out everywhere again to confirm, or Cancel to keep your sessions. On success Sentinel shows Signed out of every product and signs you out of this dashboard. If it fails, you stay signed in and see Could not sign out everywhere or the reason given; try again. This card was not checked in a browser for this guide; it is described from the source and its tests.

Sign-in alert emails

Sentinel emails you a New sign-in to your Sentinel account alert when it sees a sign-in it does not recognise. The email now names the product, for example "signed in to Uptime with password", or "Sentinel" when no product is known. If you are already signed in and a second product signs you in without asking for your password, you do not get a second alert. If you did not sign in, change your password in Profile and select Sign out everywhere.

Use Settings (General, Members, Connector keys and Billing), Profile and Reports Branding for the other settings described here.

Dashboard tour

The tour is a short seven-step spotlight of the controls around the dashboard: a welcome, the organisation menu in the top bar, Search in the top bar (find a site or a settings page by name; press Ctrl+K, or Cmd+K on a Mac, from any page), Messages, the Help button in the top bar (user guide, this tour and what is new), your account menu (profile, appearance, chart colours and sign out), and Settings in the sidebar (one link to General, members, notifications, integrations, connector keys, billing and data and privacy). It is available to every signed-in role on every plan. When Patching is enabled for your organisation, the tour has one more stop, Patching, after Settings. It points at Jobs in the sidebar and says that Jobs lists every update job and Deployments every deployment, with the counts on Home.

A new account sees it by itself, about a second after first reaching a dashboard page once setup is finished. It shows once per account. Use Next and Back, or the right and left arrow keys. Skip, the close control, and Escape all end it, and it will not start by itself again on any device. Focus returns to the page when it closes.

To see it again, select Take the tour in the Help panel. Settings no longer has a getting started card or a Take a tour button. On a phone, the Settings step points at the Settings tab in the bar at the bottom of the screen. The organisation step points at the organisation menu in the top bar. If the navigation menu is already open when a tour is due to start, the tour waits until the menu has fully closed. This also applies when you select Take a tour again.

On a phone, the Patching step points at the Jobs tab in the same bar.

If saving to your account fails, this browser still remembers that you saw the tour, but it can start again by itself on another device.