Skip to content

Add or edit a site

51 help pages

An organisation admin or site manager can use Add site or the first-site action. Viewers do not see them. The dialog lists only organisations where you can add sites. A visible add button does not mean that you have an eligible organisation to select. If the list is empty, ask an organisation admin or site manager to add the site. Enter a name and full HTTP or HTTPS URL, check the organisation, and optionally choose a security patching SLA and a maintenance update SLA, each with its own choice of how it applies. The SLA fields appear when the selected organisation's plan includes it; otherwise the dialog says why it is unavailable. Then create the record. Plan capacity is checked on the server. If refused, review billing or ask the organisation administrator.

Adding sites to a pay as you go or Agency plan

On a Pay as you go or Agency account, Add site saves the site as inactive and then opens Add sites to your plan. The site is not monitored and nothing is charged until you finish the steps below. Accounts on the older plans are not affected: their new sites are active straight away and plan capacity is checked as above.

  1. Step 1 of 2 · Choose sites. The list shows the organisation's saved inactive sites with a checkbox each. The site you just created is ticked and marked Just added. Use Select all or Clear selection, or tick other waiting sites to add them in the same payment. A summary shows how many sites you chose, Includes your free first site when the Pay as you go free site covers one, and the estimated amount Added to each renewal (the price per site times the sites that are charged, before tax). With a running subscription you pay today only for the days left in the current billing period, up to its end date; if no site is paid for yet, your first paid site starts a monthly subscription today and that date becomes your billing date. On Agency, sites within the package add nothing to the bill, so no per-site estimate is shown. Select Not now to close; the sites stay saved and inactive. Select Review price for N sites to continue.
  2. Step 2 of 2 · Review and pay. The heading reads Review N sites. Check the quote details, tick the consent box and select Confirm and pay. With an existing subscription, the amount due now is pro rata: it covers the days left until the renewal date, from that date your monthly bill is the new renewal amount, and your billing date does not change. For the first paid site, the page says this starts your monthly subscription today and renews on the same date every month after. Select Change sites to cancel the quote and go back to step 1. If the card needs attention, select Replace or verify the payment card: it opens the card verification step, and once the card is verified you return to the Sites page with the same quote. It does not start another purchase. If the quote cannot be prepared because the card is expired or not verified, select Verify or replace the payment card, then add the sites again.
  3. When payment succeeds, the message Sites added to your plan appears and the sites start to be monitored once Drupal sends data. If your bank asks for verification, complete it; you return to the Sites page and the same quote reopens so you can finish.

Sites you saved but did not add show a banner on the Sites page, for example "Example is saved but not on your plan yet" or "3 sites are saved but not on your plan yet". Select Add to plan to open step 1 with every waiting site ticked.

If you close the dialog while a payment is still waiting for your bank or needs attention, a banner says the payment has not finished. Select Continue to reopen it. The banner also comes back when you return to the Sites page later in the same browser. Until it settles you cannot start another quote or change sites on the plan.

Only the owner of the billing account who also administers each organisation involved can add sites to the plan. This includes sites in organisations covered by the owner's account. For anyone else, Add site says the billing account owner adds sites to the plan, and nothing is saved or charged; ask the owner to add the site.

Where your account is on the new prices, Add site opens the setup wizard instead of this form; see Adding a site with the setup wizard.

If the billing account owner has a Black membership (see "Black membership" under Billing), Add site does not open Add sites to your plan. The site is created active straight away, with no quote, card setup or payment, in every organisation that the owner's billing accounts cover. Organisation admins and site managers of those organisations add sites the same way, without needing to be the billing owner.

On the site page, open the Setup tab. It has a menu down the left side (below the large screen size, a Setup section list at the top). Each setting has its own page, and the address records which one is open: ?tab=setup&section=<page>. With no page named, Connection opens. A page you cannot open is not in the menu, and an address that names one opens Connection.

Setup pageWhat it holdsWho can change it
ConnectionConnection status, the four connector steps, troubleshooting.Read by everyone who can open the site.
How the site reportsThe three ways the site sends data, and where each runs. See How the site reports.Read by everyone who can open the site.
What this site reportsWhat the Connector reported, and Stack versions.Organisation admins and site managers (Stack versions).
Upgrade readinessThe Upgrade Status or Full upgrade scan in CI card. Only while upgrade readiness is on for your organisation.Organisation admins and site managers.
CertificateThe certificate check.Nobody; there is nothing to set up.
Response targetsSecurity patching SLA and Maintenance update SLA.Organisation admins and site managers.
Slack alertsSlack notifications for this site.Organisation admins and site managers.
Site detailsSite name, Site URL and Description, and Delete site.Organisation admins and site managers.

Certificate and Site details open only when the site belongs to the organisation you have selected. Response targets and Slack alerts are customer pages and do not appear in the platform administration console.

Every page has a title, a one-line description, a Guide: link and, on most pages, a Good to know box. The guide link opens the knowledge base article inside the app where the knowledge base is on (for Connection, What this site reports and Upgrade readiness), and otherwise this guide in a new tab (for example How the site reports). Each menu item shows its state in words, for example "Last sync …", "Not connected yet" or "Sync issue" for Connection, and "Security 48 hours, Maintenance 2 months" or "Not set" for Response targets.

To change the name, URL or description, open Site details. The forms on the pages for Stack versions, Response targets, Slack alerts and Site details work the same way. Save changes stays disabled until something changes. After a save, a Changes saved message appears and the form stays open. Undo changes puts back the last saved values. Viewers see the same information as plain text, with no form. The Edit site pop-up, which holds every field together, is still available from the Sites list.

Add site and first-site setup do not include Slack; add channels after the site exists, on Slack alerts. Organisation admins and site managers can choose one or more channels, keep existing settings or turn Slack off for this site. A refused Slack change does not save a partial site edit. See Workflow integrations below for the setup steps.

The site address must agree with its Drupal Connector configuration. Save the change, then update the Connector when needed.

The old addresses still work: a link ending ?edit=1 opens Response targets, and a link ending #upgrade-status opens Upgrade readiness.

Stack versions

The What this site reports page (on the Setup tab) has a Stack versions form for PHP, Web server and Database. The Edit site pop-up in the Sites list has the same fields. Use it for versions the Connector cannot see, such as a web server behind a CDN or a managed database. Each component shows an In use line: for example "Nginx 1.24.0, reported by the connector", "MariaDB 10.11.6, declared", or "Not known" when nothing has been reported or declared. Sentinel never probes your site from outside to read versions.

To declare a version, choose the product and enter the version. The web server choices are Nginx, Apache, LiteSpeed, Microsoft IIS and Caddy. The database choices are MySQL, MariaDB and PostgreSQL. PHP has no product choice. A version can only contain numbers and dots, such as 1.24.0. To remove a declaration, clear the product and version and save.

A version reported by the Connector always wins. If you have declared one as well, Sentinel keeps your value and the dialog says it is not in use because the connector reports a version. If the Connector later stops reporting a version, your declared value applies again.

Tick Installed from operating system vendor packages for a component that comes from the operating system, for example Debian or Red Hat. These vendors fix vulnerabilities without changing the version number, so matches for that component are treated as low confidence and are not shown. When Sentinel turns on its Ubuntu and Debian checks, an Ubuntu or Debian package is checked against that vendor's own security data instead, so a match the vendor says is not yet fixed in your build still shows. See The Platform list.

The declared versions are saved with Save changes, which stays disabled until you change something. Undo changes puts back the saved values. In the Edit site pop-up they save together with the other changes; if the site details save but the stack versions do not, the dialog says so, and Save changes again retries the stack versions. Sentinel checks reported and declared versions against known vulnerabilities and tells you about serious matches; see Known vulnerability alerts.

Organisation admins and site managers see the Stack versions form and can declare versions. Viewers cannot see the form; the In use lines on the Platform list show what Sentinel knows. The section is available on all plans.

Known vulnerabilities marker

The Platform panel on the site page (Overview tab) lists the Drupal core, PHP, Web server and Database versions. The web server and database appear when Sentinel has stack data for the site. Next to a version that matches known vulnerabilities, a Known vulnerabilities tag with a warning icon appears. The icon colour follows the highest open severity. Hover over the tag, focus it with the keyboard or select it to open a tooltip, for example "PHP 8.1.2 matches 4 known vulnerabilities (highest: High). Fixed in 8.1.31. This is a version check; your host may already have patched it." Press Escape to close it.

The tooltip links to View on the Platform list (the Platform chip on the Updates tab) and, while the knowledge base is on, What this means. A match comes from the version number alone. Your host may have fixed the problem without changing the version, so treat it as a prompt to check, not as proof that the site is affected.

When every match has been acknowledged, a muted check icon shows instead. Its tooltip says, for example, "PHP 8.1.2: 4 known vulnerabilities, all acknowledged as not affecting this site. Last acknowledged 12 Oct 2026 by Sam Lee."

Some versions show no marker. Not checked yet means Sentinel does not match that product (LiteSpeed, Microsoft IIS, Caddy or SQLite). PHP, Nginx, Apache, MySQL, MariaDB and PostgreSQL are all checked. Unknown means no version has been reported or declared. A version with no matches shows nothing extra.

In the Sites list, a small icon appears beside the site name for each affected component, with the same tooltip. Selecting the icon opens the tooltip and does not open the site.

Delete a site

Organisation admins and site managers can delete a site. Viewers do not see Delete site, and Sentinel refuses the request if they try another way. Open the site, select the Setup tab, open the Site details page, and use the Delete site box at the bottom of the page. Check the site name and address in the confirmation, then select Delete site again, or Cancel to keep it. If your account uses two-factor authentication, you are asked for a current code first. When the site is deleted, Site deleted appears and you return to the Sites list. If the deletion is refused, the reason shows in the dialog and the site is unchanged.

Deleting a site stops its monitoring, and its Connector can no longer send updates. The site is removed from Sites, dashboards and new reports for everyone in the organisation. Reports already issued keep it. You cannot restore a deleted site from the dashboard; contact Sentinel support if you need it back. Platform administrators do not change sites from these customer pages; they use the administration console.

Do not treat a missing list result as deletion. Check the selected organisation and search first.

Install the Sentinel Connector module

You need access to the Drupal project, Composer, and permission to enable modules and edit Drupal settings. The published Connector requires Drupal ^10.3 || ^11 and PHP >=8.3. Use the project's normal deployment process when making these changes to a live site.

The package is drupal/sentinel_connector on Drupal.org. Your project must include the Drupal Composer repository, https://packages.drupal.org/8. Projects created with drupal/recommended-project already include it; otherwise follow the Drupal Composer setup guide. From the Drupal project directory, install the supported release:

composer require 'drupal/sentinel_connector:^1.0'

Enable the module with Drush:

drush en sentinel_connector -y

Run these through the project's normal Composer and Drush environment. If Drush is unavailable, ask the site maintainer to enable the module and complete configuration. Installing the package alone does not connect the site.

Connect Drupal

Open the site's Setup tab; Connection is the first page. It gives four short steps with this site's values, and links the knowledge base article "Use the Sentinel Connector on several environments" for anything beyond one environment (while the knowledge base is off, the link opens this guide).

  1. Install and enable Sentinel Connector in Drupal with the displayed commands.
  2. Copy the Site UUID into Drupal's Configuration → Web services → Sentinel Connector settings at /admin/config/services/sentinel-connector. Connector 1.4.0 and later need no Sentinel address and no site URL: the module sends to Sentinel production by default. On a Sentinel that is not production, Setup also shows this Sentinel's API base URL to set in settings.php ($settings['sentinel_connector.api_base_url']) or the SENTINEL_CONNECTOR_API_BASE_URL environment variable.
  3. Have an organisation admin or site manager add a key for this site in Connector keys: create a new key and copy it while it is visible, or choose an existing key that you already use on another site. We recommend a separate key for each site. Store the key with the Key module, $settings['sentinel_connector.api_key'] in settings.php or the SENTINEL_CONNECTOR_API_KEY environment variable.
  4. Test the connection with Test connection on the Drupal settings form or drush sentinel_connector:check, then send the first inventory with Sync now or the displayed sync command.
drush sentinel_connector:check
drush sentinel_connector:sync

The check asks Sentinel whether the address, key and Site UUID in use work and which Sentinel answered. It stores nothing and does not count against the plan's push limit. "Site UUID not known here" usually means a production UUID on a non-production environment, or the other way round.

If something does not work, the If something does not work list on Connection starts with the check command. It also links Open this site's Connector log, to see each request Sentinel received and what it did next. A request with a refused key is not logged against the site, so run the check command when the log is empty.

In the module you also choose the Report scope (All: Drupal core, contrib and custom modules; or Drupal core and contrib, which leaves custom modules out), Report configuration drift, and Report platform versions (web server, database and operating system versions; on by default). The PHP version is always sent, because Drupal core support depends on it.

Several environments. The Site UUID, API key, Sentinel address and an off switch ($settings['sentinel_connector.disabled'] or SENTINEL_CONNECTOR_DISABLED) can each come from settings.php or an environment variable, so one codebase can send production and non-production as two Sentinel sites and send nothing from local and CI. The module ships an example include file, settings.sentinel_connector.php. The knowledge base article has the details.

Each of the four steps shows a green Done tick once Sentinel has accepted data from the site.

How the site reports. The next page in the Setup menu, How the site reports, explains when the site sends data. See How the site reports.

What this site reports. The page after that, What this site reports, has a Reported by the site card. After a push, it shows the report scope, whether platform versions are shared (with the date sharing was turned off), and the connector version with any newer release. A connector older than 1.4.0 does not report these choices; the page says so, and its menu item reads "Shown after the first sync" until the first sync. These choices are made in Drupal, not in Sentinel. The How to change these box says how: change them at /admin/config/services/sentinel-connector, then run drush sentinel_connector:sync. Sharing less means Sentinel checks less, and what is not shared is never checked.

Where the Drupal status report is turned on for your organisation, the same card has a Drupal status report line: Reporting on, Off on the site or Needs connector 1.6.0 (the connector is older, or its version is not known).

Drupal cron must run for later reports, with automatic sync on cron turned on in the Connector settings. Cron checks at most once an hour and sends only when something changed, subject to plan limits. Sentinel cannot see whether cron runs or the setting is on. Sentinel does not install Drupal updates from the dashboard. Apply updates through your normal Drupal maintenance process and send a new inventory afterwards.

Connection distinguishes Never connected, data received without an assessment, assessment in progress, assessment failed, and assessed. An accepted submission confirms receipt of inventory only.

If a module's version cannot be read, for example a Composer branch name such as dev-main, Sentinel still accepts the inventory. That module is stored with an unknown version, the same as a module whose info file has no version, so its security status is Unknown and it keeps the site Partial until a readable version is sent. Spaces around a version are removed. Only a malformed module machine name refuses the whole submission; nothing from that submission is stored.

If a new site has sent no data once the alert delay has passed since it was added (24 hours by default; Sentinel checks every 15 minutes), Sentinel sends a has sent no data since it was added alert. Usually the Sentinel Connector module has not been installed or connected yet. The email links back to this section for installation and setup instructions.

How the site reports

Open the site's Setup tab and choose How the site reports (address ?tab=setup&section=reports). Its menu hint reads "Cron, Sync now and deployments". Everyone who can open the site can read it, viewers included. It changes nothing; it explains where each report comes from.

The top of the page shows three facts: Last data received (the newest report Sentinel accepted from the site), Last Drupal.org check (when Sentinel last checked that data against Drupal.org) and Connector (the version the site reported). A fact Sentinel does not have reads Not yet, or Not reported for the Connector.

Your Drupal site sends a report in one of three ways. Each card carries a Runs on tag, because every one of them runs on your side, never in Sentinel.

WayTagWhat to know
On a scheduleRuns on your Drupal siteWhen automatic sync on cron is turned on in the Connector settings, cron checks at most once an hour and sends a report only when something changed, such as a module, Drupal core or PHP version. A quiet week with no reports can be normal. Sentinel cannot see whether cron runs or the setting is on, so if you expected a report, check both.
When you askRuns on your Drupal siteSelect Sync now on the Connector settings page (/admin/config/services/sentinel-connector), or run drush sentinel_connector:sync. Use it to test, or after a change made by hand.
After each deploymentRuns on the deployed environmentMake drush sentinel_connector:deploy the last step of your deploy script. Your CI can start the deployment, but the command runs where Drupal runs, once the new code is live. It sends a report only when the deployment changed the modules.

A line under the cards shows the path of a deployment: your CI or pipeline deploys the code, the Drupal environment runs the deploy command, and the site sends a signed report to Sentinel, which logs it and checks Drupal.org.

A report can be skipped or delayed. Cron and the deploy command skip one when nothing changed, and your plan limits how often a site can send. Each command prints what it did. Add --force to the deploy command to send one anyway. Sentinel only knows about reports it receives. A report the site skipped is not in the Connector log, and neither is a request whose key Sentinel refused. Open this site's Connector log opens the Communication Logs page for this site, for the last 7 days.

The Good to know box adds three points:

  • Sentinel cannot tell which of the three ways sent a report.
  • Each environment is its own site in Sentinel, with its own Site UUID.
  • A finished deployment is not proof that the site changed. Look for a new Last data received time.

Its Guide: link opens this section in a new tab, because there is no knowledge base article for this page yet.