Open Home for the selected organisation. This page was called Dashboard, so this section keeps that name in its title.

Security updates outstanding: known security findings. The count is exact, including zero, only when every site the dashboard shows for the selected organisation has a complete, current assessment. Sites that are inactive, deleted or belong to an inactive client are not part of the dashboard. Otherwise At least means coverage is incomplete, and Unknown is not zero. A module without Drupal.org security coverage does not by itself make a site incomplete (see the notes on alpha, beta and release candidate modules under the assessment states). Site Overview shows which sites need assessment; its expanded row shows N without security coverage for modules that have none.
Other updates: maintenance (non-security) updates outstanding across the organisation's sites. Like Security updates outstanding, it is exact only when every site has a complete, current assessment. Otherwise it counts only the fully assessed sites and reads as a minimum, or Unknown when none of them has an update.
Security score: the Overall Security Score as a number "out of 100", or Unknown while no site has been checked. It is amber below 50 and green otherwise. It is the same score as the ring below; see the Overall Security Score row. The SLA compliance rate stays in the monthly report.
Overall Security Score and Security Trend: the score is unavailable only while no site in the organisation has been checked, and it is then not recorded for that day. Security Trend charts the last 30 days of recorded scores (0 to 100) as an area chart. Sentinel records the score once per UTC day, by a daily job at 23:40 UTC. Today's point shows the current score until then. A day is recorded only while the score is available, so a day without a score shows as a gap in the chart and is never filled in. Each point is a UTC calendar day. History starts when this feature was released and is not back-filled. It is kept for 400 days and shows only while an organisation is selected. With no recorded days the panel reads "No score history yet. The trend records the Overall Security Score once a day while it is available." Do not infer a score from an empty chart. See the row below the cards.
Configuration drift: an extra card after the other figures, shown only when configuration drift reporting is turned on for Sentinel. See Configuration drift. The figure is the number of sites whose production configuration differs from code. It reads No drift at zero and Unknown when no site has a current report to compare, with "N sites unknown" under it. A quiet second line adds "N unknown" for sites that cannot be compared. Select the figure to open Sites filtered to those sites. On a wide screen (1024 pixels or more) the figures share one row; from 640 pixels they wrap; on a phone they stack as a list.
Real-time updates active: the browser is receiving live updates. Offline - Using cached data means the shown data may be old.
Risk Matrix by Site: known update counts for the displayed sites. It is not a risk score. All updates includes security updates.

Below the metric cards and the coverage note, one row holds two cards.

Overall Security Score (one third of the width) shows a ring with a score out of 100 and one sentence. Every member who can see Home sees the same score, and no plan is required.
- How a site is scored: every site that has been checked at least once gets a score. It starts at 100, then loses 25 for each security update available (a Drupal core update counts once, however many core modules the site has), 3 for each extension on an unsupported branch or without security coverage (at most 15 in total), and 2 for each maintenance update (at most 10 in total). It never goes below 0. A module without security coverage is a risk to review, not a known vulnerability, so a fully patched site stays at 75 or above.
- What a site's score rests on: a complete, current assessment (the same rule as Site Overview) gives the exact score. If the latest check of the site's current modules could not settle every module, the score is an estimate from what it did settle, and the real score may be lower. If the site has no check of its current modules yet (it has just reported a change, or its latest check failed), the score comes from its last check, before that change. A site is checked as soon as it reports its modules, including the very first time, so a new site gets a score within minutes.
- How the organisation score is worked out: the average of the site scores, rounded to a whole number, across every site that has a score. Only a site that has never been checked is left out.
- Sites left out or estimated: a site that has never been checked is left out and is never counted as healthy. The sentence then reads, for example, "Score across 8 of 10 sites (2 never checked are left out), at or above the warning level of 50." When some sites are scored from a partial or older check, it adds, for example, "1 site is scored from a partial or older check, so the score may change." With every site scored from a complete, current assessment it reads "Score across all 10 sites" and says how many security updates are outstanding across them.
- No score yet: when no site has ever been checked, the ring is a dashed empty ring with a dash and the text No score yet: "A score appears after the first check of a site, which starts as soon as the site reports its modules." An empty ring is not a good or bad score. If sites are left out because of a temporary Drupal.org problem, Sentinel retries them automatically, or you can select Re-check now on a site's page (paid plans).
Sites at a glance (two thirds) lists the first five sites by name. Searching or paging through Site Overview does not change them. Columns: Site (opens the site page), Drupal (the core version as last reported, or Not reported), Updates, Status and Last 14 days.
Updates shows the exact count only once the site's assessment is complete. At least N means the assessment is partial. Unknown means the count is not known, so it is not zero. When security updates are known, ", N security" is added.
Status shows Security update whenever a security update is known, at any coverage. Outdated or Up to date appears only with a complete assessment. No security coverage means the assessment is complete but at least one module has no Drupal.org security coverage, so the site is not called up to date. Otherwise a neutral badge says Not assessed, Assessing, Assessment failed, Assessment stale or Partly assessed. Do not read a neutral badge as healthy.
Last 14 days is a small strip with the same colours as the Site Overview Updates strip, including the split bar for a day with both kinds and the hatch for no data. A site with no history shows No history yet.
The footer reads "First N of M sites by name. Updates include security updates; unknown counts need assessment." Open Site Overview jumps to the full list below.
On a narrow screen each site stacks: name and badge, then the Drupal version and updates, then the strip.

Everyone who can see Home sees this row. No plan or setting changes it. Home opens with Waiting on you, then the figures, the fleet status strip, the Overall Security Score and Sites at a glance row, the patching target prompt for administrators (when it applies), the full Site Overview, Security Trend (full width) and Risk Matrix by Site.

Waiting on you lists what needs a person in the selected organisation. Organisation administrators, site managers and viewers all see it; each person sees only the rows their role and the organisation's plan allow.

Next steps come first when they apply. They come from the state of your sites, not from stored messages, and appear from the moment a site is added:

Add your first site: shown when the organisation has no site. The Add a site link opens the Sites page. If you cannot add sites (you are a viewer), the step reads "Ask an organisation administrator to add a site." instead.
Turn on alerts: shown with no sites. For organisation administrators, Open notifications opens Settings, Notifications. Other members see Ask an organisation administrator to turn on alerts.
{site name} is not connected yet: shown for each site that has never sent data, up to three, oldest first. Details says "This site has not sent data. Install the Sentinel Connector module, set its API key and run the first sync." Open connection guide opens the site's Setup tab. When more than three sites are waiting, a last link reads "and N more in Sites".
Next steps show a Details control. They cannot be dismissed or snoozed, they do not count in the message bell, and they are not on the Messages page. Each one disappears on its own, usually within about a minute of the site's first sync.

Rows are grouped under Critical, Needs attention and For information. Each row has one sentence, the names of the sites it covers when more than one (the first five, then "and N more"), one action link, and a Snooze control. A row appears only while its condition holds, so it clears on its own when you fix the cause.

Critical: security updates waiting (Review updates); unread critical messages (Read messages, which opens Messages showing the unread open critical messages for the selected organisation).
Needs attention: certificates that expire within 14 days, have expired or are not valid (wrong host, untrusted or invalid), while certificate checks run. The expiry date is compared with today, and a problem stays listed until a later check that reached the site clears it (Check certificate; the row is Critical when any has expired or is not valid); sites running core, modules or PHP that are no longer supported, even when the site's status shows Not secure or Sync issue first (See what is unsupported, shown only while support status is on); sites that reported before and have stopped reporting for the stale window (Check the connection).
For information: sites running an older Sentinel Connector (Update the connector); a monthly organisation report issued in the last 14 days (Open the report opens that report), shown only to people who can read reports, while the plan includes reports.

Snooze hides one kind of row for For 7 days or For 30 days. Choose a length from the Snooze control on the row. The snooze is yours alone and applies to that organisation only; other members and your other organisations are unaffected. Snoozed kinds are listed under Snoozed with "until" and the date, and Show again brings one back at once. A snoozed row returns by itself when the time ends. If the snooze cannot be saved, the row says "This could not be snoozed. Try again."

When nothing is waiting, nothing is snoozed and every site is fully assessed, the panel says All clear. Nothing is waiting on you. If some sites are not fully assessed yet, it says Nothing is known to be waiting, but not every site is fully assessed yet. Updates may still be found. When the only items are snoozed, it says Nothing else is waiting. and how many kinds are snoozed, because they may still need you. While it loads it says Loading…. If the list cannot be loaded, it says This list could not be loaded. If a later refresh fails, it keeps the earlier list and says This list could not be refreshed. Showing the earlier list. If only the next steps or only the rows fail, it says Some items could not be loaded. It refreshes every minute while the browser window is focused.

The message bell and the Messages page are unchanged. Alerts such as a site that stopped sending data stay there, and reading them there does not change Waiting on you, which is worked out from the current state of your sites.

The Messages page also accepts a severity filter in its link, which is how the Critical messages row opens it.

While the dashboard is open and focused, it checks for changed data once a minute. It refreshes affected panels when new data is available. Assessment expiry, patching deadlines and the start of a new day can also refresh a panel without a new submission from Drupal. Returning to the tab or reconnecting checks the displayed data again.

The matrix shows the first five sites in the organisation. Searching or paging through Site Overview does not change those five sites. Refreshing a panel does not send a new Drupal inventory or start an assessment.

Site Overview and history strips

Search the Site Overview by site and use its page controls to view more results. Open a site name for details. Expand Patching details to inspect outstanding advisories, deadlines, and patching results.

Switch between the SLA and Updates history strips. Point to a day, tap it, focus the strip, or use the arrow keys to read its date and explanation. Read the text and legend, not colour alone. Missing data, an unscored day, and a breached SLA are different states.

Click or tap a day to keep its details open when the pointer leaves the strip without pointing to another day. Pointing to another day shows that day's details instead. Click or tap the same selected day again to close its details. Details opened only by pointing close when the pointer leaves. Press Escape while the strip has focus, or move focus away, to close the details. Scrolling closes details opened by pointing, clicking or tapping; details selected with the arrow keys follow their day as the strip scrolls.

In the Updates strip, every bar is full height and shows one day. The legend under the list reads: Nothing outstanding, Security update outstanding, Maintenance updates outstanding, Both outstanding and No data. A Both outstanding day is a split bar, with the security colour on top and the maintenance colour below. Its explanation reads "Security and maintenance updates outstanding" and lists the security updates and the number of maintenance updates. No data is not the same as nothing outstanding.

In the SLA strip, Clear: no clock running uses the success colour only for a scored day. Days without a target stay grey or use an unscored outline. No report uses a hatch. A clear day does not erase an earlier breach.

A diamond below a bar means Security fix applied. It marks a confirmed version fix recorded for that day, not the actual deployment time. A dot above a bar means the SLA target changed. Both can appear on one day. The fix marker does not replace the day's pending or breached result. Removal, an advisory that no longer applies and an ending without recorded resolution evidence do not count as applied patches. Retrospective fix/rollback intervals without their own confirmed resolution are also excluded. Earlier confirmed version fixes remain in the history when an advisory reopens. A confirmed version fix can still have an unavailable version.

Read the day's details for the component, advisory, retained fixed version when available, observation and confirmation times, and SLA outcome in the SLA view. Missing versions or times stay unavailable. A clock can stop at an observed fix before Sentinel confirms it. A retrospective clear interval can have no separate confirmation and can show a later rollback. Patching details uses the clock stop for elapsed time and keeps confirmation separate.

When no known exposure remains open, Known security fixes applied requires a confirmed version fix in the history window. An empty window can show No confirmed outstanding findings; it does not prove a patch was applied. Breached earlier preserves the historic SLA result separately. Partial, stale, pending, failed or missing assessments still limit what is known about the whole site. Read those notices before treating a clear finding list as a complete security check.

The column header shows how many days the strip covers, for example "Last 90 days, one bar per day, newest on the right". A site with baseline access shows the last 90 days. A site without it shows the last 30 days, the same rule as the site Update history page. The strip fits as many whole days as its width allows, with today at the right. Scroll sideways with the mouse wheel, a trackpad or your finger to see older days. The small line under each strip shows the first visible day on the left and Today (or the last visible day) on the right, and changes as you scroll. The SLA strip stays at 30 days.

Colour palette

The default palette is "Red, amber, green" (earlier called traffic light): green for nothing outstanding, yellow for maintenance updates and red for a security update. To change it, open the account menu (your initials at the far right of the top bar) and choose Red, amber, green or Colour-blind safe (earlier called Okabe-Ito) under Chart colours. Colour-blind safe is the Okabe-Ito palette: green, blue for maintenance and vermilion for security. The menu closes and the new colours apply straight away. The palette applies to every chart: the security score ring, the score trend, the Risk Matrix by Site, the Updates strip and its legend, the SLA strip (scored clear days, pending days and breached days), the checked ring on the site page, the TLS certificate bar, and the bars and day strips in the monthly report, on screen and when you print it from your browser. With Colour-blind safe, a good score is bluish green, a warning score is blue and a poor score is vermilion; SLA pending is blue and SLA breached is vermilion; the Risk Matrix runs from vermilion to yellow, with sky blue for Info. In both palettes the Medium cells in the Risk Matrix have dark text. Report PDFs made by Sentinel (rather than printed from your browser) are always in Red, amber, green, and the public website previews also stay in Red, amber, green. Your choice is saved to your account, so it follows you to other devices. Before you sign in, the page uses a copy kept in your browser; once you sign in, the choice saved on your account applies, so a shared browser never carries one account's palette into another. Every signed-in role can change it, and no plan is required. If saving fails, the new palette still applies in this browser and is saved to your account on your next visit.

An administrator can set the patching target from the site controls when the plan allows it. A prompt can identify sites that have no target. It counts only sites that have sent data. It stays hidden while the organisation has no site, or while any site has not reported yet, so it does not compete with the next steps in Waiting on you. It returns on its own once every site has reported. Retry an individual panel if it fails to load; a panel error does not prove there are no sites or updates.