Open Profile to change your email, full name, date format and time zone. Use Automatic for the browser's date format. Save the form and check the result.

Time Zone. In the Profile card, Time Zone sets the zone the dashboard uses to show times to you. The default, Automatic (use my browser setting), uses your browser's zone. Otherwise pick any zone from the list; your browser's zone is marked "(this browser)". Select Save to apply it. The setting is yours alone and applies to every user, including platform administrators. If you own organisations, their schedules move with your time zone. Zone labels show names such as EDT or BST where an English name exists, and an offset such as GMT-4 where it does not.

Your time zone and date format change presentation only. An organisation's schedules use its owner's time zone (UTC if the owner has none): the days in SLA and update strips, "patches applied today", monthly report months, summary email schedules, quiet hours, update maintenance windows and AI spend weeks and months. So a strip's days can be cut in a different zone from the times shown beside it. If an email change is refused because the shared billing account is full, ask an administrator to review unused invitations and membership capacity, then retry. If the account is busy, wait briefly before retrying.

Email preferences: Profile has an Email preferences card for every organisation you belong to, with one section per organisation. Emails need a verified email address, and alerts always appear in the dashboard. Each choice saves as soon as you change it, and a message confirms it or says it could not be saved.

Security alerts: administrators, and everyone in an organisation whose Security alert audience: email all members is on, see an Always on badge; security alerts cannot be turned off. Other members see a checkbox, Email me security alerts, which is off until you opt in. Removing you from the organisation deletes your opt-in, and deleting your account or the organisation removes it too. See Messages and alerts, Security alerts on release day.
Confirmed fixes and New releases seen on your sites are checkboxes for all members. In an organisation where only administrators are emailed, members see a note that confirmed-fix and release emails go to administrators only; the security alert opt-in does not extend to them.
Configuration drift: a checkbox, Configuration drift, for every member of the organisation, viewers included. It appears only when the service has turned configuration drift on, and it is off until you opt in. When it is on, you get one email when a site's production configuration has differed from code for 48 hours. It gives the site, how many configuration objects differ, when the difference started, a link to the Drupal configuration section of the site's History tab and what to do next, including "Take a backup first, or make sure your deployment process takes one." The email does not name the objects. No email is sent if the site turned clean, or its drift state became unknown, before the 48 hours ended. If a later drift period begins, it can email again. Removing you from the organisation deletes your choice. Drift is not sent to Slack, webhooks or notification rules.
Administrators also see a Set up Slack alerts link to Integrations. It applies to the organisation selected at the top of the page.
One-time prompt: if you are not an administrator, your organisation emails security alerts to administrators only, and you have not opted in, the dashboard shows a panel under the beta notice, Get security alert emails?, with Email me security alerts, Not now and a close button. This is the same opt-in as the checkbox above. Any answer is saved on your account, so the panel does not return on any device, including for existing members who qualify the first time. You can change your choice later in Email preferences. Platform administrators do not see the panel.
The opt-in never adds you to other alerts, such as stale or missing reporting, certificate alerts or administrator-only messages. Sentinel still checks your membership, a verified current address and the site and organisation status when it sends.

Mobile number: the Mobile number card, after Email preferences, appears only when the service has phone messaging turned on. Without it, Profile has no mobile number controls. You can keep one mobile number on your account. A confirmed number can be used for two-factor codes only when the service has also turned on phone codes (see Two-factor authentication). Urgent alerts by phone appear only when the service has turned them on (see the bullets below).

Add: select Add mobile number, choose the country, enter the number and and select Send code. The dialog says "We send a code by SMS to check it is yours. Step 1 of 2.", then enter the 6-digit code. A code expires after 10 minutes. You can ask for a new one with Resend code 60 seconds after the last. After five wrong codes you need a new code. Sentinel sends at most 5 codes an hour for your account or number, and 10 an hour from one internet address; if you hit a limit, wait and try again. If you see "We cannot send codes by phone right now. Try again later.", Sentinel has paused phone codes for a while.
Waiting for confirmation: a number you have not confirmed shows this badge with Enter code and Cancel. Cancel removes the waiting number.
Confirmed: the number is shown masked, for example +61 4•• ••• 678, with the Confirmed date. The card says "For sign-in codes and urgent alerts by SMS." Australian alert messages use the sender name sentinel (lowercase). Verification codes may use a different sender. Sentinel never shows the full number again, to you, your organisation or Sentinel administrators.
Urgent alerts by SMS: when the service has turned phone alerts on and your number is confirmed, the card shows a switch, Urgent alerts by SMS. It is off until you turn it on. Without a confirmed number, or while the service has not turned alerts on, the switch does not appear. You manage alerts here only. If your phone network or a STOP reply blocks our messages, the switch turns off and a notice says when. Turn the switch back on to get alerts again; there is no reply to send. STOP does not affect sign-in codes. If a change is refused, the card says the number has opted out, is not confirmed, or that phone alerts are unavailable; try again once that is fixed. See Notification rules for which alerts are sent and how.
Change number: starts again with a fresh code for the new number. The old number gets no further messages. While phone codes are on, it needs a step-up with your authenticator app or a recovery code (a phone code is refused), and sign-in codes go to the new number only after it is confirmed.
Remove: deletes the number from your account straight away. While phone codes are on, it needs the authenticator app or a recovery code, and it turns phone codes off.
Security email: Sentinel emails you when a number is confirmed, changed or removed. If you did not make the change, change your password in Profile and select Sign out everywhere.
Disabled by support: support can disable a number; the card then says so. Support disabling is not available yet.

Deleting your account deletes the number and its message records.

Use Change Password with your current password and matching new passwords. The new password must differ from the current one, and changing it restarts your password expiry period (see Password expiry). A provider-only account uses Add a password, which sends the password recovery flow. After recovery, sign in with the new password and re-link providers as needed.

Google and GitHub linking controls appear when enabled. Confirm your current Sentinel password before linking or unlinking. Keep a working sign-in method. The page can require adding a password before removing a provider link.

Settings pages

Settings is one area with a menu on the left (a grid of buttons on a phone), described under Navigation and organisation selection. Opening it goes to the first page you may use. Your own details are in My profile, and your personal email choices are in the Email preferences card in Profile; Settings has no personal security controls. The pages are:

General (Settings → General, every member): the organisation's name, description and country, Require two-factor authentication for all members and Security alert audience: email all members (see Organisation details), Make default, and the organisation's sites. Administrators also see the Security card for the password rotation period (see Password expiry). A member who is not an administrator sees the details without the controls that change them. This is the page that Organisation settings in the organisation menu opens.
Members (Settings → Members, every member): the page that was called Users, now titled Members. See Invite and manage members.
Notifications (Settings → Notifications, administrators only): Notification rules and the weekly summary, described below. Who receives security alert emails is set in General.
Integrations (Settings → Integrations, every member): Slack workspace connection and account linking. Choose site channels in Edit site.
Connector keys (Settings → Connector keys, organisation admins and site managers): the keys your sites use to send data to Sentinel. The page was called API keys and its heading is now Connector keys. See the API keys section.
Billing: Overview, Upgrade (or Plans), Payment methods and Invoices, for an administrator who can read billing when billing is switched on. The row of section tabs that used to sit across the billing pages is gone; use the Settings menu.
Data and privacy (Settings → Data and privacy, every member): the data processing agreement panel and Delete organisation. Administrators act; other members see the existing section behaviour. Data export and retention have no customer page, so they are not here (see Ask for a copy of your data).

Notification rules are on the Notifications page of Settings for the selected organisation. You must be an active administrator of that organisation. Creating or changing rules, previewing notifications and sending tests require baseline report access, including current site approval where required. Your administrator role is checked separately. Without that access, you can still view rules and delivery status, and delete existing rules. Deleting the last rule for an event type restores its default delivery. An Agency customer organisation uses its subscription holder’s plan. Where billing is disabled, the existing report-access compatibility applies. Managers and readers cannot manage rules or view delivery status.

Select Create rule, enter a Rule name, and select at least one optional event: Recovered, Release observed, or Patch resolved. You can filter by Severities, Sites, and exact Components. An empty filter matches all available values in that organisation. Severities offers only values supported by the selected events. Recovery has no component evidence. When recovery is selected, remove existing component filters before saving; you can still deselect them, but cannot add new ones. If a previously selected site is no longer in the active catalogue, it remains shown as unavailable. Deselect it explicitly before saving; the form does not silently remove it and widen the rule to other sites. Clearing every site selection matches all organisation sites, so review the remaining scope. A selected component that leaves the catalogue also remains shown as unavailable and must be removed before saving. Clearing every component selection matches all components; no missing selection is removed automatically. Select Save rule. Each organisation can have up to 50 rules.

Also send by SMS: the rule form has a fieldset, Also send by SMS. It is for urgent events, and it is available only when the service has turned phone alerts on. Tick Send critical events in this rule by SMS to choose Critical events to send by phone: Security update needed, Site down (stopped sending data), Certificate expires soon and Certificate expired. The form shows how many members will get them, for example "2 of 5 members will get them". These events are always emailed, whatever your rules say. Selecting them in a rule controls phone delivery only, and email cannot be turned off in a rule. The rule's sites, severities, pause and quiet hours apply to the phone message. Component filters cannot be used with these events. Without a plan that includes phone alerts, the tick box is disabled and says "Phone alerts are on paid plans", with See plans. The rule list shows "Sent by: Email" and, for these rules, a Phone chip.

A phone alert goes to the members who would get the email, narrowed to those who have a confirmed number, and have turned on Urgent alerts by SMS in Profile. For Australian numbers, the SMS uses the sender name sentinel (lowercase). The sender used in other countries can differ. Each SMS ends with "Turn off in your Sentinel profile." Each member gets one phone message per event. Several security updates for one site queued together arrive as one message with a count. The message holds only the site name, a count and a dashboard link. If a matching rule has quiet hours, the phone alert waits until they end. If the problem is resolved during quiet hours, nothing is sent. Each organisation can send 300 phone alerts a calendar month (UTC) by default. The Also send by SMS section shows Phone alerts this month: X of N. When the limit is reached it adds "Monthly limit reached. Urgent alerts still go by email. Phone alerts start again on" the first day of next month, and phone rules in the list show "Phone paused: monthly limit". Organisation administrators get one Messages notice a month, "Phone alerts paused: monthly limit of N reached". Phone alerts need a paid plan; phone sign-in codes work on every plan.

If Sentinel as a whole sends too many phone codes in an hour (a fraud guard), new urgent alerts go by email only for a while.

Rules control optional email. In-app messages remain available under their usual access rules. With no rules for an event type, its default delivery applies. Once that type has rules, an event must match at least one active rule. Overlapping matches do not create duplicate emails. Pause stops a rule from matching; another active rule can still allow the event. Resume does not send a backlog of suppressed events. Use Delete, then Confirm delete, to remove a rule. Removing the last rule for a type restores that type’s defaults.

Use quiet hours delays matching optional notices until the window ends in the saved organisation owner's time zone, including daylight saving changes. If several rules match, the earliest permitted delivery wins; a matching rule without quiet hours permits immediate delivery. Ready fix and release events can be emailed first, with deferred events in a later email. These custom quiet hours do not delay the complete in-app notice. Newly confirmed fixes refresh the same notice on the normal grouping schedule while email waits. Its later refresh retains valid events and removes fixes that are no longer confirmed. The service’s separate general quiet-hours setting still applies. Deferral before queueing does not start an email retry period. If quiet hours begin during a retry, the same queued email waits within its original expiry period. A later rule suppression or membership change can cancel queued content. A delayed recovery notice is suppressed if reporting has become stale again; recovery never means that a site has no security issues.

Required alerts are always on means rules cannot suppress or delay security, missing or stale reporting, or TLS alerts. Normal email availability and recipient checks still apply. TLS alerts remain restricted to organisation administrators. Destinations are eligible members with verified current addresses, subject to Security alert audience: email all members in Settings → General. A personal choice that turns off confirmed-fix or release email in Email preferences still applies. Rules cannot add another address. Tags and SLA breach event rules are unavailable.

Under Preview and test saved rules, save your changes first. Select a site, event, its actual severity, and any applicable components, then select Preview saved rules. The result shows whether the sample is allowed, deferred or suppressed, with active matching rules and an eligible-recipient count. Paused rules are excluded. A deferred time is shown in your browser’s local time. You must add a site before preview or test is available.

Send test to me queues a labelled sample only to your current verified address. It does not create or change a monitoring condition, and it does not prove that a real event matches the rules. You can send at most three tests per hour across organisations. Queue acceptance does not prove inbox delivery.

Recent delivery status shows policy and email-processing metadata. Use Refresh delivery status for a new check. Not queued can mean suppression or deferral; an empty list does not prove that a site is healthy. Expired, failed and uncertain email outcomes appear in delivery status. An uncertain outcome means Sentinel cannot confirm whether the provider accepted the email. Provider acceptance does not prove inbox delivery. If loading fails, use Retry notification rules. For an access error, check the selected organisation, your administrator role and its plan. After changing organisations, review that organisation’s saved rules before making changes.

Sessions and signed-in products

Profile has a Sessions and signed-in products card above Delete account. It 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.

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.

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.

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.

Settings pages

Sessions and signed-in products

Sign-in alert emails

Dashboard tour