Lets a connected AI read the site's Elementor widgets and their settings, and add, change, duplicate, move and remove Elementor's own widgets on a page, following your approval settings, with undo. Undo restores the page's data rows in place. A site whose Elementor version builds widget settings only in the editor gets a plain explanation that those settings are unavailable.<\/p>","0.61.165":"
Lets a connected AI create and edit designed Elementor draft pages in the colours, fonts, spacing and corner style the AI chooses for them, with ready-made sections and undo. On a block theme, the page fills the screen without the theme's header and footer. Saving refreshes the stylesheet once and keeps the template and page settings; undo restores them exactly.<\/p>","0.61.164":"
Edits of an Elementor draft that someone has previewed now go through, and an edit or undo refused because the page is open in an editor can be tried again once it is closed. Reading the structure of an Elementor draft the AI can edit also says whether it is open in an editor or has unsaved changes.<\/p>","0.61.163":"
Lets a connected AI read an Elementor page and edit a draft it created, with your approval for each edit and an undo for each change. WPMgr needs this version on the site for it. Nothing is published.<\/p>","0.61.162":"
Backup uploads retry temporary storage errors and name the cause when they fail. Core updates are skipped on Composer-managed sites and report the installed version afterwards, and a core rollback needs an explicit instruction from WPMgr. The listing no longer says backups are encrypted: this plugin does not encrypt them.<\/p>","0.61.161":"
Lets a connected AI create a draft page or post in Elementor from an outline, with your approval for each request in WPMgr. Nothing is published, and undo moves the draft to the trash.<\/p>","0.61.160":"
Lets a connected AI create a draft page or post from an outline with real layout, with your approval for each request in WPMgr. Nothing is published. Also keeps each cache purge's report separate when one purge starts another.<\/p>","0.61.159":"
Adds two read-only facts to the site details sent to WPMgr: the parent theme of a child theme and, where Elementor runs, whether its Atomic editor is switched on. It changes nothing on the site.<\/p>","0.61.158":"
Lets a connected AI read published content and, with your approval in WPMgr, change page and post titles and excerpts, with undo. Also runs reviewed read-only tools from other plugins.<\/p>","0.61.157":"
Improves AI page creation: titles and text with "&" or bracketed numbers are stored as literal text, and an interrupted request's untouched draft can be moved to the trash.<\/p>","0.61.156":"
Adds AI page creation, off by default and turned on per site from the Content tab. A person approves each request in WPMgr. Pages are always created as drafts by a dedicated content user that cannot log in, and can be moved to the trash while untouched.<\/p>","0.61.155":"
Adds a signed command the control plane uses to list the tools (abilities) a site registers and to run WPMgr's own read-only abilities. It changes nothing on the site. It sends the names, labels and descriptions of registered abilities, with each one's owner type, site facts (WordPress and PHP versions, theme and active plugin names), and, for a published page without a password that the control plane asks for, that page's title and text.<\/p>","0.61.154":"
Adds a read-only check the control plane can run to see which editor owns each page and whether it is a special page. It changes nothing on the site and does not send page body text or stored builder data; it sends published page titles and, for a single page, editor display names.<\/p>","0.61.153":"
The plugin can now carry out a cache purge limited to this site's own page cache, skipping hosting and CDN cache integrations, and report which integrations ran, when the control plane requests it.<\/p>","0.61.152":"
Detects when a stored key no longer opens, shows an admin notice naming which and what to do, and refuses a backup with a clear reason when the backup key cannot be used.<\/p>","0.61.151":"
Router log lines now escape control characters, so a command failure always reads as one line in the debug log instead of one that could break apart. What is sent to the control plane is unchanged.<\/p>","0.61.150":"
Command failures are now diagnosable from the dashboard: the kind of error, where it was thrown, and a redacted reason, plus a matching line in the site's debug log. Also adds a content-update command for changing an existing post's title or body; nothing in the dashboard uses it yet.<\/p>","0.61.149":"
Fixes a media quarantine restore that could overwrite a file recreated at the same path, and could remove a quarantined file it had declined to restore. Also tightens where the page cache and folder creation may write. Update if this site uses the unused-image quarantine.<\/p>","0.61.148":"
Fixes a white screen on Enroll on hosts without the native libsodium PHP extension, common on shared hosting, cPanel and CloudLinux in particular, where the plugin installed and activated normally but enrollment could not be completed. Update to complete setup on those hosts. Also removes a settings section that referenced a dashboard flow that was never built.<\/p>","0.61.147":"
On a multisite network, plugins activated for the whole network are now reported as active, so they stop being missing from the plugin inventory and from the update and vulnerability checks that read it. This plugin's licence is also now declared as MIT consistently across every surface that states one. Safe to update in place.<\/p>","0.61.146":"
The application-password two-factor control now actually takes effect: if this site has two-factor authentication enabled, an application password will stop working for a user who has a second factor enrolled or whose role requires one, returning HTTP 401. Review any integration on this site that authenticates with an application password before updating. Also fixes a database restore that could write into live tables while reporting success, and a user-agent ban that could lock administrators out of the login page.<\/p>","0.61.139":"
Email delivery failures are now detected on sites that send through their own SMTP setup, not only sites routed through WPMgr, and a plugin bug that reported a failed send as successful is fixed: wp_mail() now returns false on a failed send. Forms and other flows that check the result of wp_mail() will start correctly reporting failures they previously hid. Safe to update in place.<\/p>","0.61.131":"
Fixes a bug that could silently delete this site's working SMTP password when its email settings were saved, tested or synced from the dashboard, breaking outgoing email. Update now if this site sends mail through SMTP, SES, SendGrid, Mailgun or Postmark; the dashboard restores the password automatically on its next sync with this site.<\/p>","0.61.127":"
Password policies can now target the roles your site actually has, including roles added by WooCommerce, membership, LMS and booking plugins, shown in the site's own language. Safe to update in place.<\/p>","0.61.114":"
Updates and rollbacks on one site now run strictly one at a time, so two WordPress installers can no longer run against the same site at once and corrupt an update in progress. Safe to update in place.<\/p>","0.61.112":"
Fixes outgoing email failing completely when a plugin sets a Reply-To, To, Cc or Bcc header in the "Name " form, which WooCommerce and many form plugins do by default. Update if this site sends mail through SMTP or SendGrid.<\/p>","0.61.95":"
Failed backups no longer leave their working files on the site, which could be more than a gigabyte, and the cleanup no longer depends on WP-Cron. Safe to update in place.<\/p>","0.61.85":"
Fixes full backups failing at the upload stage on slow servers. The agent now reports progress during long archive and encryption passes. Safe to update in place.<\/p>","0.61.25":"
Fixes a restore bug that could silently drop plugin or theme files whose path contained a reserved drop-in name, leaving a restored site broken while reporting success. If a restore on an older version left a site broken, re-restore the same snapshot on this version.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":2},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3636102,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3636102,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3636102,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3636102,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3636102,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.61.127","0.61.131","0.61.139","0.61.146","0.61.148","0.61.149","0.61.150","0.61.151","0.61.152","0.61.153","0.61.154","0.61.155","0.61.156","0.61.157","0.61.158","0.61.159","0.61.160","0.61.166"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The WPMgr dashboard. Every site you manage in one list, with its status, pending updates and tags.","2":"This plugin's own settings screen in wp-admin before pairing: a Control-plane URL to save, then a Pairing code to enroll. Nothing happens until you supply both.","3":"One site's Backups tab: a completed run, the destination it went to, and the restore history.","4":"Updates across every connected site, with the pre-update snapshot available to roll back.","5":"Performance: Core Web Vitals from real visitors, page cache state and image optimization.","6":"Security: hardening switches, login protection, and the vulnerability findings the dashboard matched for this site."}},"plugin_section":[],"plugin_tags":[151,247,600,174442,2550],"plugin_category":[54,59],"plugin_contributors":[274597],"plugin_business_model":[],"class_list":["post-324501","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-performance","plugin_tags-security","plugin_tags-site-management","plugin_tags-updates","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-mosamlife","plugin_committers-mosamlife"],"banners":{"banner":"https:\/\/ps.w.org\/fleet-agent-site-manager\/assets\/banner-772x250.png?rev=3636102","banner_2x":"https:\/\/ps.w.org\/fleet-agent-site-manager\/assets\/banner-1544x500.png?rev=3636102","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/fleet-agent-site-manager\/assets\/icon.svg?rev=3636102","icon":"https:\/\/ps.w.org\/fleet-agent-site-manager\/assets\/icon.svg?rev=3636102","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\n
Fleet Agent Site Manager securely connects the WordPress sites you look after to a WPMgr dashboard, so backups, updates, caching, security and performance for every one of them run from a single screen.<\/strong><\/p>\n\n You need a WPMgr dashboard as well as this plugin.<\/strong> Run one on your own server for free (it is open source: https:\/\/github.com\/mosamlife\/wpmgr), or use the hosted service at https:\/\/manage.wpmgr.app.<\/p>\n\n Until you enter a dashboard address and complete a signed pairing, this plugin has no endpoint, opens no outbound connection and sends nothing anywhere.<\/p>\n\n Every action the dashboard can ask for is on a closed, named list compiled into the plugin, and each one is verified against an Ed25519 signature tied to that pairing before it runs. There is no eval, no remote include and no remote PHP execution of any kind.<\/p>\n\n Backups and restore.<\/strong> Full and incremental backups of the database and files, scheduled per site or run on demand. An incremental run uses a content-addressed chunk store so only changed blocks move. Send them to storage the dashboard manages, a folder on your own server, or your own S3-compatible bucket. Restore a whole site or pick components, with a health check afterwards and an automatic rollback if the site does not come back.<\/p>\n\n Updates you can undo.<\/strong> Core, plugin and theme updates across every connected site, applied by WordPress's own Upgrader against WordPress.org packages. A snapshot is taken before each one, so a bad release is one click back rather than a restore from last night's backup. A watchdog recovers a site whose update died mid-write.<\/p>\n\n Speed.<\/strong> Disk page cache with an nginx and Apache fast path that serves a hit without booting PHP. Optional Redis object cache. Remove Unused CSS, CSS and JavaScript minification, deferred JavaScript, speculation rules, CDN rewriting, lazy iframes, and self-hosted Google Fonts, Gravatars and third-party scripts.<\/p>\n\n Images and fonts.<\/strong> Convert the media library to WebP and AVIF, keep the originals, and put them back if you do not like the result. An unused-image cleaner finds files nothing references. TTF, OTF and WOFF are transcoded to WOFF2.<\/p>\n\n Security.<\/strong> Hardening switches that stay off until you turn them on: file editor, XML-RPC, REST, author enumeration, SSL and HSTS, directory browsing, PHP execution in uploads. Login protection with per-site IP, CIDR and user-agent bans enforced at earliest boot. A hidden login address. File-integrity scanning against WordPress.org checksums and a learned per-site baseline.<\/p>\n\n Two-factor for your site's own users.<\/strong> Authenticator app, emailed code or single-use backup codes, with guided enrollment once you require it for a role.<\/p>\n\n Password policy.<\/strong> Minimum strength, reuse blocking, optional expiry, and a breach check that never lets the password or its full hash leave the site. Policies target the roles your site actually has, including roles added by WooCommerce, membership and LMS plugins.<\/p>\n\n Database tools.<\/strong> Scan for revisions, transients, spam and orphaned metadata, preview exactly what will go before anything is deleted, take a snapshot before any change, and run a serialization-aware search and replace.<\/p>\n\n File manager.<\/strong> Browse, read, write, rename, delete, chmod, search, upload, archive and extract, with a version history on writes and a restore. Guarded against executable writes and protected roots.<\/p>\n\n Site email.<\/strong> Route this site's outgoing mail through Amazon SES, SendGrid, Mailgun, Postmark or SMTP, with per-sender routing, automatic fallback, suppression of known-bad addresses and a full send log.<\/p>\n\n Real User Monitoring.<\/strong> Off by default. Turn it on and Core Web Vitals come from your actual visitors, page by page, instead of one lab score.<\/p>\n\n Cache purge reaches the layer in front of WordPress too, detected automatically: Varnish, Kinsta, WP Engine, SiteGround, Cloudways, RunCloud, GridPane, SpinupWP, CloudPanel, Rocket.net and WP Cloud, plus Cloudflare once you add its API credentials to wp-config.php.<\/p>\n\n The expensive work runs on the dashboard rather than on your server: unused-CSS computation, image and font encoding, vulnerability matching against a managed feed, uptime probing and site screenshots.<\/p>\n\n This plugin is MIT-licensed and the dashboard is AGPL-3.0. Source for both: https:\/\/github.com\/mosamlife\/wpmgr<\/p>\n\n This plugin contacts nothing until you connect it to a WPMgr control plane you choose, self-hosted or the hosted service at https:\/\/manage.wpmgr.app. There is NO default endpoint: it is inert until you supply a control-plane URL and complete a one-time, signed enrollment.<\/p>\n\n Once connected, the agent communicates only with the control-plane URL you configured. It sends the following, only to that endpoint, and only for the management actions you or your schedules initiate:<\/p>\n\n The agent does not sell or share this data with third parties.<\/p>\n\n Real User Monitoring (when you enable it)<\/strong><\/p>\n\n Real User Monitoring (RUM) is off by default and must be enabled per site. It is the one exception to the agent-as-sole-transmitter model above: the agent adds a small, public measurement script to HTML it already serves, and your visitor's own browser, not the agent, then sends anonymous performance measurements directly to the control plane.<\/p>\n\n What the visitor's browser sends:<\/p>\n\n What is never collected: cookies, localStorage, cross-site identifiers, or the visitor's full IP address. The IP is used only transiently for rate-limiting and coarse country lookup, then discarded and never stored.<\/p>\n\n This data originates from your visitors' browsers, so you (the site owner) are its data controller and must disclose it in your own site's privacy policy. If you self-host the control plane, RUM data stays entirely on your own infrastructure and never reaches WPMgr. If you use the hosted service at https:\/\/manage.wpmgr.app, that service processes the measurements on your behalf.<\/p>\n\n Disable RUM at any time in the Performance settings; the script is removed from newly cached pages immediately.<\/p>\n\n If you connect to the hosted WPMgr service, its Terms of Service (https:\/\/manage.wpmgr.app\/terms) and Privacy Policy (https:\/\/manage.wpmgr.app\/privacy) apply. If you self-host the control plane, you operate the receiving service and your own policies apply. You can stop all data transmission at any time by disconnecting the agent (Disconnect in the agent admin screen) or deactivating the plugin.<\/p>\n\n How it works \/ security<\/strong><\/p>\n\n Commands arrive from the control plane over HTTPS. Each carries an Ed25519 signature produced with the key established at enrollment, and the agent verifies it before executing any action. The allow-list of permitted commands is compiled into the plugin, no mechanism exists to add new command types at runtime, and there is no eval, remote include, or remote PHP execution. Core, plugin, and theme updates are applied using WordPress's own Upgrader against wordpress.org packages only.<\/p>\n\n This plugin contacts external hosts only after you connect it to a control plane, and only for the specific features you enable. The plugin is inert until connected. This build contains no self-update client; updates arrive through the WordPress.org directory only.<\/p>\n\n WPMgr control plane (the URL you supply)<\/strong><\/p>\n\n What is sent: site URL and name, WordPress and PHP versions, active plugin and theme inventory, Site Health results, rendered HTML of selected pages (for used-CSS computation), backup archives, transcoded font bytes, and cache and performance statistics.\nWhen: on enrollment, diagnostics, heartbeat, backup progress, cache and performance operations, Remove Unused CSS, autologin token consumption, database clean, font transcoding, and password breach checking. Always triggered by an action or schedule you initiate, never autonomously.\nWhy: this is the dashboard that manages the site.\nHosted at https:\/\/manage.wpmgr.app, its terms and privacy policy apply. Terms: https:\/\/manage.wpmgr.app\/terms Privacy: https:\/\/manage.wpmgr.app\/privacy\nSelf-hosted, you operate the receiving service and your own policies apply.<\/p>\n\n Have I Been Pwned (https:\/\/haveibeenpwned.com), reached via the WPMgr control plane<\/strong><\/p>\n\n What is sent: the first 5 characters of the SHA-1 hash of a candidate password, a k-anonymity range query. The site sends that prefix to the WPMgr control plane, which relays it to the Have I Been Pwned range API (https:\/\/haveibeenpwned.com\/API\/v3#searchingPwnedPasswordsByRange) and returns the matching hash suffixes. The password itself, the full hash and the user's identity never leave the site; the agent compares the remaining 35-character suffix locally.\nWhen: only while the optional password-policy breach check is enabled, and only when a site user sets or changes a password. Off by default.\nWhy: to refuse a password already known to be breached.\nTerms: https:\/\/haveibeenpwned.com\/TermsOfUse Privacy: https:\/\/haveibeenpwned.com\/Privacy\nThe control-plane hop is covered by the WPMgr terms above.<\/p>\n\n Object storage (configured by your control plane)<\/strong><\/p>\n\n What is sent: backup archives (not encrypted by this plugin), restored backup chunks, optimized media files and transcoded font bytes, over short-lived presigned URLs the control plane supplies. No storage endpoint is hardcoded in this plugin.\nWhen: during backup, restore, and media or font optimization operations that you initiate.\nWhy: this is where your backups and optimized assets are stored.\nThe hosted service uses Google Cloud Storage (storage.googleapis.com) by default; a self-hosted operator may configure any S3-compatible destination. For the hosted default, Terms: https:\/\/cloud.google.com\/terms Privacy: https:\/\/policies.google.com\/privacy<\/p>\n\n ipify (https:\/\/api.ipify.org), operated by ipify (https:\/\/www.ipify.org)<\/strong><\/p>\n\n What is sent: nothing. A plain GET request carrying no site data; the response is this server's public outbound IP address, cached locally for 8 hours.\nWhen: during diagnostics collection, which you run or schedule.\nWhy: to infer which host the site runs on.\nTerms: https:\/\/geo.ipify.org\/terms-of-service Privacy: https:\/\/geo.ipify.org\/privacy-policy<\/p>\n\n Cloudflare API (https:\/\/api.cloudflare.com), operated by Cloudflare, Inc.<\/strong><\/p>\n\n What is sent: the configured Cloudflare zone ID and the API credentials you placed in wp-config.php.\nWhen: on a cache purge, and only while the Cloudflare integration is active. It stays inactive unless you define CLOUDFLARE_EMAIL and CLOUDFLARE_API_KEY, or CLOUDFLARE_API_TOKEN, in wp-config.php.\nWhy: to purge the Cloudflare edge cache so visitors do not keep an old page.\nTerms: https:\/\/www.cloudflare.com\/website-terms\/ Privacy: https:\/\/www.cloudflare.com\/privacypolicy\/<\/p>\n\n Google Fonts (https:\/\/fonts.googleapis.com, https:\/\/fonts.gstatic.com), operated by Google LLC<\/strong><\/p>\n\n What is sent: the font-family request derived from the page, the same request a browser would otherwise make.\nWhen: on cache build, and only while the self-hosted fonts optimization is enabled and a page uses Google Fonts.\nWhy: to download the CSS and WOFF2 files server-side and serve them from your own domain instead.\nTerms: https:\/\/policies.google.com\/terms Privacy: https:\/\/developers.google.com\/fonts\/faq\/privacy<\/p>\n\n Gravatar (https:\/\/gravatar.com, https:\/\/secure.gravatar.com), operated by Automattic<\/strong><\/p>\n\n What is sent: the avatar hash derived from the page.\nWhen: on cache build, and only while the self-host Gravatars optimization is enabled.\nWhy: to download avatar images server-side and serve them from your own domain instead.\nTerms: https:\/\/wordpress.com\/tos\/ Privacy: https:\/\/automattic.com\/privacy\/<\/p>\n\n Third-party asset hosts referenced by your own pages<\/strong><\/p>\n\n What is sent: a plain GET request to a cross-origin script or stylesheet URL that your page already references.\nWhen: on cache build, and only while the self-host third-party assets optimization is enabled.\nWhy: to serve those assets from your own domain instead.\nThere is no single provider. The hosts depend entirely on what your own pages embed, and the applicable terms and privacy policies are whichever of those hosts publish.<\/p>\n\n Email delivery providers (only the one you select, if any)<\/strong><\/p>\n\n What is sent, for every provider below: sender address, recipient addresses (To, Cc, Bcc), subject, message body (HTML and\/or plain text), and attachments or attachment metadata.\nWhen: only when that provider is the active email transport for this site and an outgoing email is sent. No provider is active until you configure one.\nWhy: to deliver this site's outgoing mail through a provider rather than the server's own mailer.<\/p>\n\n matthiasmullie\/minify (MIT)<\/strong><\/p>\n\n CSS and JavaScript minification uses matthiasmullie\/minify (^1.3, MIT), a pure-PHP library in the plugin's Composer dependencies. Copyright (c) 2012 Matthias Mullie. Source: https:\/\/github.com\/matthiasmullie\/minify<\/p>\n\n matthiasmullie\/path-converter (MIT)<\/strong><\/p>\n\n matthiasmullie\/path-converter (~1.1, MIT) is minify's own Composer dependency, rewriting relative paths in minified CSS, installed into the same vendor tree. Copyright (c) 2015 Matthias Mullie. Source: https:\/\/github.com\/matthiasmullie\/path-converter<\/p>\n\n bjeavons\/zxcvbn-php (MIT)<\/strong><\/p>\n\n Password-strength scoring in the password policy uses bjeavons\/zxcvbn-php (^1.4, MIT), a pure-PHP port of zxcvbn in the plugin's Composer dependencies. Copyright (c) 2013-2014 Benjamin Jeavons. Source: https:\/\/github.com\/bjeavons\/zxcvbn-php<\/p>\n\n symfony\/polyfill-mbstring (MIT)<\/strong><\/p>\n\n symfony\/polyfill-mbstring (>=1.3.1, MIT) is zxcvbn-php's own Composer dependency, providing mbstring functions where the extension is absent, installed into the same vendor tree. Copyright (c) 2015-present Fabien Potencier and contributors. Source: https:\/\/github.com\/symfony\/polyfill-mbstring<\/p>\n\n No other third-party PHP libraries are bundled beyond those credited above. Image encoding and WOFF2 font transcoding run on the control-plane service, not inside this plugin. The bundled Real User Monitoring JavaScript also carries a third-party library; see Source code below.<\/p>\n\n This plugin ships two minified JavaScript files. Their human-readable source and build tooling are in the public repository at https:\/\/github.com\/mosamlife\/wpmgr<\/p>\n\n Click Disconnect<\/strong> on the same settings screen, or deactivate the plugin. All outbound communication stops immediately.<\/p>\n\n\n Yes. This plugin is the agent that runs on your site, and it needs a WPMgr dashboard to talk to. That is either a WPMgr instance you run yourself (open source, https:\/\/github.com\/mosamlife\/wpmgr) or the hosted service at https:\/\/manage.wpmgr.app. On its own the plugin does nothing at all.<\/p><\/dd>\n WPMgr is the project. This plugin is its agent, listed in this directory under the name the plugin directory approved, and the project's own code and documentation call it the WPMgr agent. One plugin, one repository: https:\/\/github.com\/mosamlife\/wpmgr<\/p><\/dd>\n No. The dashboard is AGPL-3.0, has no site limit when you run it yourself, and nothing in it is gated behind a paid tier. Running it does mean running the control-plane service, PostgreSQL and object storage, plus the encoder service if you want image, font and unused-CSS optimization, and a free Wordfence Intelligence API key if you want vulnerability matching. The install guide is in the repository.<\/p><\/dd>\n Self-hosted, as many as your server will carry. The hosted service has per-plan limits, listed at https:\/\/wpmgr.app\/pricing<\/p><\/dd>\nWhat you can do once a site is connected<\/h4>\n\n
Privacy \/ What data is sent and where<\/h3>\n\n
\n
\n
External services<\/h3>\n\n
\n
Third-party \/ Credits<\/h3>\n\n
Source code<\/h3>\n\n
\n
\n
What you need before you start<\/h4>\n\n
\n
How to disconnect<\/h4>\n\n
\n
Do I need anything besides this plugin?<\/h3><\/dt>\n
Why is this called Fleet Agent Site Manager when the dashboard is called WPMgr?<\/h3><\/dt>\n
Is self-hosting a cut-down version?<\/h3><\/dt>\n
How many sites can one dashboard manage?<\/h3><\/dt>\n