A site has no Patching settings or schedule until it is enrolled. Enrolling is done by an organisation administrator or a site manager, with a recent second-factor code if they have set one up. Charges come from the number you approve under Sites to cover, not from enrolling: each enrolled site uses one of those sites, and enrolling adds no charge by itself. Where we arranged your access, Sites to cover does not apply.
What members and administrators see. On a site that is not enrolled, the Patching tab says Patching is not turned on for this site. Administrators and site managers see Enrol this site. Other members see "Ask an administrator of (organisation) to enrol this site." Administrators and site managers can also select Enrol on the site's row in the Patching column of Sites.
The wizard. Enrol this site opens a page at /app/patching/enrol/(site) with a stepper that shows the current step and works on phones: Start, AI provider key, Repository, Deployment, Checks, Mode, Schedule and Review. Where package exclusion editing is enabled, Exclusions comes immediately after Repository, once the repository and Composer path are confirmed.
- Start. Use a saved profile (see Profiles) or choose Set up step by step. The default profile is listed first but never preselected. A profile that needs attention is disabled, with the reason shown.
- AI provider key. Choose from a list of your keys. Each shows its provider, the model Sentinel runs on, how many enrolled sites use it and its spend cap. The organisation's default key is preselected. The last option, Add a new key, opens the add-key form inline; Save key and select it saves the key and selects it. Next is disabled while that form is open. Under the options a Patching AI panel shows the Patching AI notice and clause 17.6 of the Terms in full in a scrolling panel, with links to "Terms of Service, version …" (the version the text names), "Privacy policy" and "Data Processing Agreement" (your organisation page; all open in a new tab), and one box: "I am authorised to accept these Terms for my organisation and instruct Sentinel to use the AI option selected above. This box does not accept the Data Processing Agreement, which is accepted on the organisation page." Read the text to the end (or select Jump to end) before the box can be ticked; Next stays disabled until you tick it. Selecting Next records the acceptance for this website and the AI option you chose (Included AI or a key), under your name; the panel then reads "Patching AI terms accepted for (website), by you." If your organisation is in the European Union, the European Economic Area, the United Kingdom or Switzerland, the AI agent does not run until an organisation administrator has accepted the Data Processing Agreement on your organisation page; the Patching tab shows that as a step. If the website later uses another AI option, or the text changes, the AI agent does not run for it until an organisation administrator accepts again: its Patching tab shows the step Accept the Patching AI terms for this website with the AI key it uses, marks the website Needs attention, and shows a Patching AI terms card with the same text. Read it to the end, tick the box and select Record acceptance.
- Repository. If no Git host is connected yet, the step says Connect where this site's code lives with Connect GitHub and Connect GitLab.com; you come back to this step when you are done, with your draft kept and the new account picked, and a notice such as "GitHub connected. Pick the repository below." Otherwise choose a repository from the list (see Choosing a repository under Git hosts for what each row shows, Refresh list and Can't find your repository?). Each repository can belong to one site. After Choose, only that repository stays on screen while Sentinel checks its access; Cancel returns to the list. When the check passes, a card with a green tick shows the repository, its connection and default branch, with Change and Remove (organisation administrators); when it fails, the card gives the reason with Try again and Choose another. When the Git host takes too long, the reason is "The Git host took too long to answer. Nothing was saved; choose the repository again." Choosing that same repository again then saves it. When another save changed the repository while it was being checked, the reason is "Another save changed this site's repository while it was being checked. Refresh and choose it again." When another site took the repository a moment earlier, the reason is "This repository is already used by (site name). Each repository can belong to one site.", or "This repository is already used in another Sentinel organisation. Each repository can belong to one site." if that site is in another organisation. Someone who cannot see the repository list (a site manager) gets "This repository is already used by another site. Each repository can belong to one site." in both cases. Then set the production branch (what the live site deploys from; security update pull requests always go into it), the branch for maintenance updates (it starts as the production branch), the branch prefixes and the Composer path. Pull requests into a branch other than the production branch are not deployed by Sentinel: with Autopilot, Sentinel merges a maintenance update into that branch and you promote it. Sentinel names the branches it creates from the prefixes:
release/for security updates andmaintenance/for maintenance updates unless you choose others, for examplerelease/security-20261022-1a2b3c. A prefix must end with/and must not be the start of the production branch or the branch for maintenance updates. - Deployment. Choose how updates reach production: "Sentinel merges, my pipeline deploys" (no hosting connection needed), "Sentinel merges and follows my hosting platform" (then map the production environment, or skip it for now) or "I merge and deploy myself" (no hosting connection needed). See Who deploys updates.
- Checks. Sentinel runs the repository probe, checks for CI on pull requests, the CI tests rule (see Automated tests in CI) and hosting. A failed check says how to fix it. Select Run checks again once you have.
- Mode. Choose Copilot or Autopilot, and the Data residency country if your account offers more than one (see Data residency). Autopilot is disabled and marked Not available yet when the CI tests rule is not met (Deploy waits for tests is not enough for Autopilot, unless an organisation administrator has let Autopilot merge before the tests run once that is turned on for your organisation; see Autopilot when your deploy waits for tests) or the organisation has no active Patching access. Choosing Autopilot opens its settings: the runtime components with a per-component Autopilot switch, and three stop switches (require client approval, the maximum number of open pull requests from 1 to 3, and start paused). A website paused this way shows Autopilot is paused for this website on its Autopilot card, if that card is available to you. An organisation administrator selects Turn Autopilot on to start it, or applies a profile with the box clear. Resume does not clear this pause. Scheduled runs skipped until then do not run again, and runs already waiting go on. Then read the Autopilot terms to the end (or select Jump to end); you can also open Read the Deployment terms you also accept, because turning on Autopilot accepts those terms as well. Tick the box and type the website name. The consent is recorded for this website under your name. Once required checks are turned on for your organisation, the Checks step has a Required checks row, and Autopilot also needs an acknowledgement on this step (see Required checks).
- Schedule. Titled "When should updates run?". It applies to both Copilot and Autopilot and has a Security updates card and a Maintenance updates card (see Schedules). The update kinds are chosen here, with each card's Enabled switch.
- Review. A summary with Edit links (including a "Patching AI terms" line that reads "Accepted by you, now" or "Not accepted yet"), the price line, and optionally Save these choices as a profile with a Profile name and Make it the default profile. Select Enrol this site. If the CI tests rule fails while Autopilot was chosen (for example through a profile), Review offers Enrol in Copilot instead. If Sentinel has no acceptance for this website and AI option when you enrol, the wizard returns to the AI step (or to Review when you used a profile) with "Accept the Patching AI terms for (website) with the AI option it will use, then enrol." Tick the box, continue, then enrol again.
Using a profile. Choosing a profile fills in the key, branches, mode, both schedules and data residency (the Schedule step is marked "From profile"). You choose the repository, package exclusions where enabled, and who deploys (the deploy method is set for each site, never in a profile); the checks run on Review. A profile's hosting connection is optional: the profile form offers "None, or choose for each site". A profile never accepts terms, so an Autopilot profile still asks for this website's own Autopilot terms, and the Patching AI panel appears on the Review step until you tick its box. Enrol this site waits for that tick.
Drafts. Your choices are saved automatically as a draft ("Draft saved · the key itself is never kept in a draft"). A draft keeps choices only, never a key. The site's Patching tab shows "You started enrolling..." with Continue and Discard draft.
An enrolled site. The top of the Patching tab shows an Enrolled card with a Copilot or Autopilot pill, Needs attention when something needs a person, and the enrolment date and profile name. Open the card to read the full enrolment sentence and the reasons. Administrators and site managers see Unenrol there. See The site Patching tab.
Unenrol. A confirmation explains that the schedule stops, no new runs start, queued jobs are cancelled, and, if you pay per site, the site comes off the bill at the next renewal, or the one after if that invoice is already being prepared. The minimum number of sites on your plan stays on the bill until you remove Patching. The site's configuration, pull requests and history are kept, and you can enrol it again.
Profiles
A profile is a saved set of enrolment choices: AI key, Git and hosting choices (the production branch, the branch for maintenance updates and the two branch prefixes), mode and both schedules. Open Settings → Patching → Profiles. Only organisation administrators manage profiles; other members read the table.
The table shows Profile (with a Default badge and any warnings), Mode and schedule (the pill, then the security and maintenance schedules), AI key, Git and hosting, Sites enrolled and Updated. Administrators can use Edit (shown as Fix when the profile needs attention, for example because its key was revoked), Duplicate, Set as default, Apply to sites and Delete. Deleting a profile leaves its sites as they are. New profile opens the profile form.
A profile is a copy, not a link. Editing a profile changes no site until you apply it.
Apply to sites. Choose sites to apply the profile to. A preview table per site shows Setting, Now, After and Result:
- Will change and No change.
- Needs terms: the website has no Autopilot terms of its own, so it stays on Copilot. Once required checks are turned on for your organisation, Will change, mode needs acknowledgement means the website needs its own required checks acknowledgement, so it stays on Copilot. A profile never gives one.
- Mode blocked: the site cannot use that mode (for example Autopilot is not available).
The repository and the hosting environment are never changed. Tick I have checked the changes for these sites. and select Apply to N sites. If something changed since the preview, a new preview is shown for you to confirm again.
Connecting a Git host
An organisation administrator (with a recent second factor) connects a Git host under Git hosts with Connect GitHub or Connect GitLab.com. A dialog first lists the permissions the host will ask for. Choose Continue to GitHub (or Continue to GitLab.com) to leave Sentinel for the host, approve it there, and you return to the Connections page. A notice at the top says the connection worked or what went wrong.
- GitHub installs the Sentinel GitHub App. On GitHub, choose Only select repositories to limit it to the repositories you will update. The App asks for write access to repository contents and pull requests in that one approval, and the row shows Updates enabled. The person installing it must own the GitHub account or organisation the App goes on (an organisation owner, or the user for a personal account); a collaborator's installation is refused with a notice asking an owner to start the connection. If a row shows Read-only, the installation has not accepted write access yet: use the enable updates on GitHub link and accept it on GitHub. The badge then changes to Updates enabled.
- GitLab.com has a with updates (write access) tick box in the dialog. Without it the row shows Read-only and says to connect again with updates when you want them.
- We recommend one GitHub organisation or account for each Sentinel organisation. Sharing one is possible, with the limits below.
Dialogs that connect an account, save a key or ask for consent also show How we keep this secure (opens in a new tab). It opens the Patching security article and leaves the dialog as it was. The link shows only while the article is available to you.
The buttons are disabled, with an explanation, when your deployment has no GitHub App or GitLab application set up, and for members who are not administrators. Members who are not administrators do not see Git host rows or repository lists, so give your own customers a role that is not administrator.
Sharing a GitHub account between organisations. GitHub allows one App installation per account, so a second Sentinel organisation shares the first one's. We recommend avoiding this: every organisation depends on one installation, so uninstalling or suspending it on GitHub disconnects all of them, and GitHub owners and administrators of the first organisation can still reach the account's repositories. Clause 4.3 of the Terms of Service makes this your decision. To share, you must own the GitHub account and administer both organisations. In the second organisation choose Connect GitHub, then Use an account that already has the App in the dialog. Do not use Continue to GitHub for an account that already has the App: GitHub stops at that account's settings page and does not return to Sentinel. Use an account that already has the App sends you to a GitHub sign-in. When you return to Connections, a panel says Choose the GitHub account to connect to and the organisation's name. It lists the GitHub accounts you own that have the App. An account that another organisation already holds is marked "Connected to another organisation, so it will be shared". Select Connect on the account you want (this needs a recent second-factor code). The panel then says GitHub is connected. The sign-in lasts ten minutes and only works for the person who started it; if it has run out, or someone else opens the link, the panel says "This GitHub sign-in has expired or belongs to someone else. Start the connection again." Start again from Connect GitHub. If you do not own the account, or do not administer both organisations, the connection is refused with the notices described below. The row shows a Shared badge and starts with no repositories. Choose Choose repositories, tick the ones this organisation may use, accept the risk and choose Save repositories. That organisation then sees only those repositories. A repository belongs to one organisation, so one already in use shows Used by another organisation. Taking a repository away removes it from its sites, stops tracking their open pull requests and stops any running update. Removing a shared connection leaves the App installed until the last organisation removes it, and the organisation that connected first must remove its connection last. Someone who does not administer both organisations sees "This GitHub account is connected to another Sentinel organisation." GitLab.com accounts cannot be shared.
If the host stops accepting a connection (the App is uninstalled or suspended, or the GitLab token is revoked), the row shows an error. Sites using it are marked repository disconnected until it is connected again; their configuration is kept. One email goes to an organisation administrator when this happens.
Choosing a repository. The picker is the same on the enrolment Repository step and on a site's Patching tab, and organisation administrators choose (the list needs the Patching configure permission, as before). Each repository can belong to one site, across every Sentinel organisation. A repository another site uses is greyed out with no Choose button. It says Used by (site name), a link to that site's Patching tab, when that site is in your organisation, or Used in another Sentinel organisation (the site is never named). A site of your organisation whose client is archived or inactive shows Used by another site. An archived repository is greyed out too: "Archived on the host. Unarchive it to use it." Your site's own repository shows Current and Check again. Sites that already shared one repository keep working until one of them changes its repository, and deleting a site frees its repository for another. If a deleted site is restored after another site took its repository, the restored site has to choose a repository again.
Refresh list sits next to the search box. Sentinel asks the Git host at most once every 15 seconds for each connection; otherwise it shows the cached list. If the Git host cannot be reached, a red message says so and that the list below may be out of date.
Can't find your repository? This panel stays under the list while you pick. Sentinel can only list repositories it has been given access to, so a private repository that is missing must be added on the Git host first.
- GitHub. Select Add a repository on GitHub. It opens the Sentinel App's installation settings on GitHub in a new tab, and the panel changes to Waiting for you to finish on GitHub with three steps: under Repository access choose Only select repositories and add the repository, select Save, then come back. After you save, GitHub may show a Sentinel page in that tab that says "Saved on GitHub". Close that tab and go back to the enrolment. Open GitHub again, I'm done, refresh now and Stop waiting are there if you need them. Only a GitHub owner can change the App's repositories, so if that is not you, use Copy link and send the link to an owner. The list refreshes when you return to the tab and every few seconds for up to 2 minutes. If nothing new has arrived the panel says "No new repository yet. Did you click Save on GitHub?" Repositories that appear are placed at the top with Just added, and a note says "1 new repository found".
- GitLab. Select Add a project on GitLab. Invite the GitLab user that connected Sentinel to the project with the Developer role or higher, then come back and refresh.
- Another account (enrolment only). On the enrolment Repository step the panel also offers It's in another GitHub account and Connect GitLab.com, which start the connect flow. Afterwards you land back on the enrolment Repository step, not Patching settings, with the new account picked and your draft kept.
- Another host. Code on Bitbucket or somewhere else? Ask us to support it opens the integration request form.
Only GitHub.com and GitLab.com are supported. For GitHub Enterprise Server, self-managed GitLab, Bitbucket, Azure DevOps or a plain Git remote, select My repository is not listed under Git hosts (or on a site's Patching tab). It opens a form at Patching requests, and Which hosts are supported? explains the list. Started from a site's Patching tab, the form already has that site selected; otherwise choose the site the request is about. The form says: "We support GitHub.com and GitLab.com. Describe your repository host and we will evaluate whether we can add it. A typical evaluation takes one week; we will reply on this ticket."
It asks for the repository host (GitHub Enterprise Server, Self-managed GitLab, Bitbucket, Azure DevOps or Another host), the host URL, your organisation or group name, whether the host is reachable from the internet, the CI system you use and the number of sites. Choosing a host Sentinel knows but does not support yet shows a Known limitation note explaining why, so you learn it at once. Do not put tokens or query strings in a URL; the form refuses them.
Sending the form creates a ticket (SNTL-n) in your Support, with your answers on it, and our staff reply there. Sentinel keeps the URL on the ticket only; it is never used as configuration. If you send the same form again for the same site while your ticket is still open, your answers are added to it as a reply (sending identical answers adds nothing) (and the ticket is reopened if it was waiting on you or resolved) instead of a second ticket. Once the ticket is closed, a new request opens a new ticket. Any member of the site's organisation, member or administrator, can send a request. The forms are available only when Patching is enabled for your organisation and Support is available.
