No. MainWP's connection layer to child sites, its update orchestration, and its backup integrations all keep doing their job. SleekView is a row-level view and inline-action layer over the data MainWP already stores on the dashboard install. The MainWP UI continues to be the configuration home; SleekView gives you better daily ops surfaces.

MainWP runs on a dedicated WordPress install — the dashboard site — and stores child-site records, sync state, update queues, and history in its own custom tables (typically prefixed mainwp_). SleekView reads those tables directly when run on the dashboard install, the same way it reads any other custom table.

Yes. Row actions call MainWP's own API endpoints — sync, run pending updates, trigger an on-demand backup — so the work goes through the same code paths as the native UI. The actions respect MainWP's permissions and capabilities; SleekView just makes them reachable from a saved view.

MainWP extensions add tables and option keys (Pro Reports, iThemes Security, backup integrations). SleekView reads what's there: extension tables become available data sources, extension status flags become columns. It doesn't duplicate extension features — it surfaces their data alongside MainWP's core data.

Yes. SleekView views are gated by WordPress capability and can be filtered. Tag each child-site record with a client identifier (custom field in MainWP supports this), then save a per-client view scoped to that tag, gated to a specific role. The account manager logs in and sees only their sites.

Queries hit MainWP's indexed columns (id, url, client_id, last_sync) and use keyset pagination where possible. Aggregate columns (summed pending updates) are computed in SQL not PHP. For very large fleets, scope default views by client and let drill-downs go wider, so a casual click doesn't full-scan every record.

Yes. SleekView routes the action through MainWP's API rather than writing directly. That means MainWP's filters and actions — pre-update, post-update, child-site notification — fire exactly as they would from a manual click in MainWP's own admin. Audit trails stay consistent and any reporting extension picks up the action.

Yes. Any saved view exports to CSV with the visible columns and current filter applied. Useful for monthly client reports, internal audits, or providing a snapshot to non-WP stakeholders without giving them MainWP access. Combine with MainWP Pro Reports if you already use it.