Sites
Browse and filter the fleet, act on many sites at once, and add or retire a site.
The Sites screen is the fleet list. It is where you find a site, narrow the fleet down to a set worth acting on, and run something across that set.
Three views
The view switcher above the list offers Table, Cards and List.
Table is the default. Its sortable columns are Site, Environments, Provider, Core and Visits / wk. Each row carries a checkbox, a small screenshot thumbnail, the site name with its account underneath, and clickable environment chips that jump straight into that environment. A site awaiting deletion wears a Removal chip.
Cards shows a larger screenshot per site with a health dot, the account name, a meta line reading provider, WordPress version and weekly visits, the environment chips, and a WP Login pill that signs you into production.
List is one section per site with a row per environment. Each environment row shows a screenshot, an environment badge, the core version, the home URL, visits and storage, and two buttons: Manage site and WP Login.
Right-click the view switcher (title="Right-click to set your default view") to set which view Sites opens in. The picker reads “Default: Table”, “Default: Cards” and “Default: List”, ticking the current one, and switching immediately. The choice is stored per browser.
Search and filters
The search box is labelled Filter sites… and matches on site name and account name. It does not search plugins, themes or URLs.
To add a filter, click + Filter. That opens a two-level menu: pick a category, then pick a value from a searchable list where each option carries its site count. The five categories are:
- Provider
- Backup
- Core
- Theme
- Plugin
Only active filters render as chips. A chip reads its category, then its value, for example Provider · Kinsta. Each chip carries a chevron and an ✕ (title="Remove filter") that clears just that filter. When two or more conditions are active, an AND / OR pill appears. A Clear link resets the search box, every filter and every selected label at once.
Plugin and theme sub-filters
The Plugin and Theme chips open a wider popover instead of a plain list. It holds a Version section and a Status section, each with its own IS / IS NOT toggle, and a footer link reading ✕ Remove plugin filter or ✕ Remove theme filter.
Version and status options are sorted by site count, largest first. Picking one keeps the popover open so you can stack selections. A negated version shows in the chip label as ≠, and a negated status as not, so a stacked chip reads like Plugin · elementor-pro · ≠ 4.2.3 · inactive.
Theme and plugin filtering runs on the server. The Manager asks for the fleet’s filter options, then posts your selection and intersects the returned site ids with the list. Provider, Backup and Core are applied in the browser.
Filters are not written into the URL and are not saved, so a filtered list is not a shareable link.
Labels
When any site in view carries a label, a Labels: row appears under the filters with one chip per label. Each chip shows the label icon, its text and a count. Clicking chips toggles them, and multiple selected labels are OR-ed together.
Labels are operator notes that do not change a site’s lifecycle status. They are created and removed with wp captaincore site-label, not from the dashboard. See WP-CLI commands for the types and options.
Two operator-only pseudo-labels ride in the same row. removal requested filters to sites awaiting deletion, and unassigned filters to sites with no account.
Pinned sites
Right-click any site row and choose Pin to top. Pinned sites appear as chips in a strip above the list, each with a health dot, the site name and an ✕ (title="Unpin"). The strip is built from the whole fleet, so a pinned site stays visible even when the current filter excludes it. Pins live in your browser.
Bulk actions
Table view rows carry checkboxes. The header checkbox selects every filtered site across all pages, not just the visible page.
With anything selected, a bar appears reading N selected with these actions:
- Sync data
- Update WP
- Back up
- Apply HTTPS
- Scan errors
- Open in console
The first five run against each selected site’s production environment and ask for confirmation first, for example “Update WP on 12 sites (production)?”. The selection clears when the run dispatches. Open in console keeps the selection so you can adjust it before running.
A Clear link at the right of the bar drops the selection.
Targeting a filtered set in the console
Whenever a filter actually narrows the list, a chip appears beside Clear reading Console · 47 (title="Target these sites in the console"). Clicking it opens the terminal dock with every matching site’s production environment preselected, across all pages, and toasts how many environments it targeted. The chip only shows when a filter is active, so a stray click cannot target the whole fleet.
Sorting, paging and counts
Table headers sort the whole filtered set before it is paged, and the active header gains a ↑ or ↓. Paging is explicit, not infinite scroll. Page sizes are 24, 48, 96 and 240, and the choice persists per browser. The footer reads like 1–24 of 2910 sites · page 1 of 122 with Per page buttons and «, ← Prev, Next → and » controls.
The pill beside the screen title counts the fleet, reading 2910 sites · 3412 environments, or Loading fleet… while hydrating.
Adding a site
+ New site in the top bar opens a dialog with four tabs. Operators get all four, customers get the first two.
New provisions a site at Kinsta. Fields are Site name (capped at 32 characters with a live counter that stays red until it reaches 5), Domain, Provider (only when more than one Kinsta connection exists), Datacenter, Clone from and, for operators, Accounts. The button reads Create on Kinsta.
The Datacenter dropdown is searchable. Beside it is a map-pin button (title="Find the nearest datacenter to the customer's location") that opens a place search. Type the customer’s city or address, press Search, pick a match, and every datacenter is ranked by distance with the closest selected automatically. You can pick any row from the ranked list instead. Place search is credited in the dialog as “Place search by Photon · OpenStreetMap data”.
Clone from starts at None (fresh install) and otherwise lists Kinsta sites on the selected provider connection only, because Kinsta cannot clone across companies. The Datacenter field is hidden while cloning, since the clone API ignores region.
Under Accounts, an operator adds accounts to the new site and marks one as Customer and one as Billing. If no customer account is set, the site is placed in a new account.
Request is the customer path. It submits a site name, an account and free-text notes to operations.
Import from provider connects sites that already exist at a connected provider. Sites already in the fleet are skipped.
Connect manually onboards a non-provider site with a server address, SFTP user and password, protocol and port, and a choice of Production only or Production + Staging.
Site requests
Customer requests appear as a queue on the Sites screen itself, between the pinned strip and the list. Both roles see it.
Each request card shows the requested name, the account and a Site request pill, then three step pills with dates: Requested, Preparing and Ready. Operators move a request along with Continue and Back, edit it with Modify, and close it with Finish at the last step or Cancel before that. Modify opens a dialog titled “Update site request” with New site URL, Name and Notes.
Removing a site
Removal is requested from the site’s own page, not from this list. See Site detail.
A site marked for removal keeps its row here, wearing the Removal chip, and operators can filter the queue with the removal requested label chip.
What customers see
Customers see only their own sites, and every count and filter option derives from that narrower set. They do not get the removal requested or unassigned chips, the Import from provider and Connect manually tabs, or the operator-only Accounts block in the New site dialog. On the request queue they see the step pills and the Cancel link, but not Modify, Back or Continue.
Everything else on this screen is the same for both roles, including the terminal, since the server scopes command runs to the caller’s own sites.