SleekView Charts for Notification by BracketSpace
BracketSpace Notification stores every rule in wp_notifications (v9) or a CPT (v8). SleekView Charts rolls those rows into active-alert donuts, carrier breakdowns, and trigger-family bars.
♾️ Lifetime License available
Notification rules are infrastructure, chart them
BracketSpace Notification is a powerful trigger-and-carrier engine, but its admin list shows each rule as a title and a status. The trigger key (post/published, user/login_failed, plugins/updated), the carrier (Email, Slack, Webhook), the recipient string, and the last-updated timestamp all hide behind the editor screen. On a site with thirty or forty rules across security, editorial, and integration destinations, that single-column list is the bottleneck before any actual logic runs.
SleekView Charts reads the same storage Notification writes to (the v9 wp_notifications custom table or the legacy CPT) and aggregates. Total active rules, carrier distribution as a donut, trigger family as a horizontal bar, and rules updated per month as an area chart turn alert configuration into a queryable surface. Each chart respects the same masking the Tables view applies, so secret webhook URLs stay hidden in exports.
Charts and Tables share the same data layer, so a filter applied on the SleekView Notification table (carrier equals Slack, status equals Active) reshapes every chart on the dashboard. The plugin keeps owning triggers, carriers, merge tags, and the queue logic that fires each rule. SleekView Charts adds the audit and ops layer notification configuration needs once you pass a handful of rules.
Workflow
From notification rules to a configuration dashboard
Detect storage version
Promote rule fields
Pick configuration KPIs
Trend rule activity
Sample dashboard
Charts you can build from BracketSpace Notification data
Active rules
Count
Rules by carrier
Count
group by carrier
Trigger family breakdown
Count
group by trigger
Rules updated per month
Count
group by updated_at
Comparison
Default Notification reporting vs SleekView Charts
Notification admin
- Default list hides carrier and recipient distribution
- No aggregate dashboard across rules
- Trigger-family breakdown requires manual counting
- Carrier-coverage gaps are invisible
- Stale-rule cleanup has no chart surface
SleekView Charts
- Active-rules Number card for ops audits
- Carrier donut for at-a-glance coverage check
- Trigger-family bar to separate security from editorial
- Configuration-churn area chart per month
- Masked exports keep secrets out of audit files
Features
What SleekView Charts gives you for Notification by BracketSpace
Carrier coverage donut
Distribution of rules across Email, Slack, Webhook, and other carriers in one shape. Over-reliance on a single carrier surfaces before an outage proves it.
Trigger separation
A horizontal bar of rules per trigger family separates security alerts from editorial flow and platform integrations. Each owner sees their slice.
Stale-rule detection
An area chart of rules updated per month shows configuration freshness. Long flat stretches flag the rules nobody has touched in a year.
Audience
Who builds Notification charts dashboards with SleekView
Security audits
A donut of security-trigger rules by carrier and a bar of failed-login alert routes. Auditors get a one-screen answer instead of a per-rule walkthrough.
Editorial ops
Trigger-family bars scoped to post/* events confirm every editorial step has the right notification wired to the right inbox or Slack channel.
Cleanup runs
Configuration-churn area chart highlights rules untouched in over a year. Bulk-disable stale notifications from retired plugins or old campaigns from the matching table view.
The bigger picture
Notifications need an audit surface, not just an editor
Notification rules drift quietly. A login-failed alert points at a Slack channel archived six months ago. A webhook URL leads to a staging endpoint from 2024.
A post/pending_review email goes to an editor who left the company. None of that shows up on the default list screen, which displays only titles and on-off badges. The first time anyone notices is when an incident happens and the alert that should have fired did not.
Treating notification configuration as a chart surface turns drift into a visible signal. A donut of carrier distribution surfaces over-reliance on one channel. A bar of trigger families separates security from editorial so each owner sees their slice.
An area chart of rules updated per month flags the rules nobody has touched in over a year. SleekView Charts reads both v8 and v9 storage transparently and masks secrets in exports, so audits stay clean. The plugin keeps owning trigger logic and carrier delivery; the charts add the audit layer alert configuration deserves once it stops fitting on one screen.
Questions
Common questions about SleekView Charts for Notification by BracketSpace
Yes. The chart layer checks which storage format is active and reads the legacy CPT or the newer wp_notifications custom table transparently. Sites mid-migration with rules in both formats see them merged across every chart card.
 No. Webhook URLs, API tokens, and any field flagged sensitive stay masked. The mask works at render time and at export time, so audit CSVs do not leak values for users without the right capability.
 Yes. Slack, Discord, Twilio, Telegram, and any other carrier extension that registers with Notification appears as a value in the carrier dimension. Custom carriers chart the same way built-in ones do.
 Yes. Per-role row scoping applies to chart aggregations so a security-scoped editor sees only auth-related rules in their dashboard. Capability checks run on read, so scoped users cannot bypass the slice by URL manipulation.
 Yes. The updated_at timestamp is available on every rule. An area chart of rules updated per month surfaces configuration churn; a flat stretch flags rules untouched in a year, candidates for cleanup.
 Yes. Charts and Tables share the same data layer. A filter on the SleekView Notification table (carrier equals Slack, status equals Active) reshapes every chart card. Drill-down stays consistent across the two views.
 No. Charts are observational; bulk actions happen on the SleekView Notification table. Click a chart segment to scope the table to that cohort, then run the bulk-disable action there. The two layers compose cleanly.
 No. BracketSpace Notification still owns triggers, carriers, merge tags, and queue logic. SleekView Charts adds an audit and ops layer on top, using Notification's own data. Disabling SleekView Charts leaves every rule and its history untouched.
 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