SleekView Kanban view for MainWP
SleekView reads the MainWP tables directly, groups each client site by its current review state, and lets the team drag cards across Pending, Updates due, Scheduled, Healthy so the underlying record updates the moment the column changes in WordPress.
♾️ Lifetime License available
Why MainWP client sites fit a kanban view
MainWP writes each client site to wp_mainwp_wp with metadata in wp_mainwp_wp_sync. Each row has an ID, a created timestamp, a responsible user, a severity tag, and the message rendered in the admin. The default MainWP screen is a paginated table, fine for browsing and weak when a agency owner needs to know which client sites are still open this week.
SleekView Kanban reads the same wp_mainwp_wp rows the MainWP dashboard queries. Pick the review state field as the grouping column and every entry becomes a card under Pending, Updates due, Scheduled, Healthy. Card fronts show the message, the username, the severity, supporting metadata, and the timestamp so the agency lead can prioritize work from one board without a CSV export.
Dragging a card between columns writes a review workflow tag back to the MainWP metadata. A move from Updates due to Healthy flips the tag and timestamps the action. The plugin's notifications and scheduled scans keep running, so a manual triage move never silences a fresh alert that arrives during the same minute.
Workflow
From the MainWP table to a live security board
Connect MainWP as a source
Pick the review state column
Choose card front fields
Enable drag-and-drop writeback
Sample board
Sample MainWP triage board view
Comparison
Default MainWP vs SleekView Kanban
Default MainWP dashboard
- Long sortable table of client sites with no triage queue for open work
- Severity filter reloads the page and loses the user filter just set
- No visual sense of which client sites are active versus resolved already
- Marking a record reviewed needs the per-row context menu and dialog
- Coordinating the weekly review needs admin rights and MainWP training
SleekView Kanban
-
Reads directly from
wp_mainwp_wpandwp_mainwp_wp_sync - Drag a card to Healthy and the MainWP review tag writes atomically
- Cards show message, username, severity, context, and timestamp
- Column counts update live so a spike of high severity surfaces fast
-
Per-role caps tie writeback to
manage_optionsfor the team
Features
What SleekView Kanban gives you for MainWP
Native MainWP model
Every column maps to a real review state derived from the MainWP workflow tag stored in metadata. Notifications, scheduled scans, and external mirrors keep running for new client sites, so a manual triage move never silences a f
Drag-and-drop with trail
Each move writes a review entry into the MainWP metadata naming the analyst who dragged it, the source column, the destination column, and the timestamp. If a lead pushes a card back from Healthy to Scheduled, the chain of custo
Saved board views per shift
Filter to high severity for the on-call analyst, configuration changes for developers, and unresolved cards older than seventy-two hours for the security lead. Each saved view becomes a shareable URL that opens the right board.
Audience
Where a MainWP kanban changes security work
Weekly review session
Security leads scope the board to the last seven days, drag high severity into Updates due, and confirm Healthy only once every Pending card has a documented decision. Next week starts with a board
Incident response workflow
On-call analysts pull the Scheduled column during a suspected incident, watch related client sites land in Pending, and coordinate on the same board instead of a Slack thread that loses context afte
Developer change review
Developers scope the board to file change and role change records, confirm each matches a documented deployment or contractor task, and Resolve them so the weekly review focuses on truly unexplained
The bigger picture
Why this view matters for MainWP work
MainWP captures everything, which is exactly what makes the default screen hard to use across a security team. The sortable table is great when an analyst knows what they want and almost useless when a agency owner needs to coordinate a week of client sites that all need a documented decision. Most teams export a CSV, drop it into a sheet, and tag records by hand.
The sheet drifts within days. New client sites keep landing in MainWP without a workflow tag, the sheet records resolutions that nobody copies back, and by month end the two views disagree on what is still open. A kanban view that reads and writes the same MainWP metadata as the dashboard keeps the team and the source of truth aligned.
Pending surfaces immediately. Scheduled cards stay visible across shifts. Healthy client sites carry a documented decision and a named analyst, all without leaving WordPress.
Questions
Common questions about SleekView Kanban for MainWP
Live. SleekView queries the same wp_mainwp_wp and wp_mainwp_wp_sync tables the MainWP dashboard reads. Filters apply at the SQL level, so a board scoped to the last seven days reflects records that landed in the last seven days, not yesterday's snapshot exported elsewhere.
No. SleekView writes a review workflow tag into the MainWP metadata. External notification destinations like email, Slack, and webhooks keep operating on the original record, so the tag never replays an alert, never suppresses one, and never alters the metadata that mirrors already sent.
Yes. The site_id column on every MainWP row tags records with their originating subsite. SleekView exposes that field as a filter and a board grouping option, so a network admin can scope to a single subsite or split each subsite into its own column for focused triage.
Yes. Every move runs through current_user_can('manage_options') and the MainWP admin capability before any metadata write. A contributor account can drag for personal sorting but the change does not persist, with a toast notification explaining why the move was rejected by the system.
Filters are applied at the database query level rather than in JavaScript. A typical board scopes to the last seven days, to one severity, or to in-progress states only, so the rendered card count stays under a thousand. Older records remain queryable in archive views without slowing the live board.
Yes. Severity lives on wp_mainwp_wp and supporting context lives in wp_mainwp_wp_sync. SleekView exposes both as card fields, so an analyst can spot repeat patterns across high severity records and queue them for action without leaving the kanban board for separate queries elsewhere.
Yes. Premium features add external destinations, reports, and search filters. SleekView reads the same metadata fields, so premium features like file integrity monitoring and external session tracking surface their client sites on the same board for unified triage across the workflow.
Yes. Every drag writes a review entry into the MainWP metadata naming the user, source column, destination column, and timestamp. The entry uses the MainWP metadata API so audits, exports, and downstream automations can read the trail without needing a separate event log table.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout