✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for Notification by BracketSpace

SleekView Kanban reads Notification by BracketSpace rules straight from the WordPress database, groups them into statuses like draft, active, paused, and disabled, and lets your team drag cards across lanes to enable, pause, or retire rules without ever leaving WordPress.

♾️ Lifetime License available

SleekView Kanban board for Notification by BracketSpace

Why Notification rules need a kanban view

Notification by BracketSpace stores every notification rule as a row in the notification custom post type, with a trigger, a carrier list, a recipient set, and a post_status that tracks whether the rule is currently active, paused, or in draft. The default admin list shows these rules as a flat post table with a status column. That works when a site runs ten notifications, but quickly turns into noise once an integration-heavy WordPress install has hundreds of rules wired to triggers, carriers, and recipients.

SleekView Kanban reads the same notification rule rows and groups them by status, which is the natural pipeline column for this plugin. Each card surfaces the rule title, the trigger, the carrier list, and a relative time stamp so an admin can scan a column without opening every rule. Disabled and draft rules sit in their own lanes instead of cluttering the active list, and paused rules are obvious instead of mixed in.

Dragging a card from one column to another writes the new status back to the same notification post, so the trigger dispatcher, carrier registrations, and recipient lookups all stay in sync. Bulk drags update every row in a single transaction, so a stack of fifty draft rules can be activated in one sweep instead of opening each one to flip its status individually.

Workflow

From rule list to kanban in four steps

1

Point SleekView at Notification

Install SleekView, then pick Notification by BracketSpace from the data source picker. The plugin auto-detects the notification post type, every trigger, and every carrier registered on the site. No queries to copy, no schema to map by hand, just confirm the rules look right in the preview.
2

Pick rule status as the kanban column

Open the view config and set the group-by field to notification post status. SleekView reads every value the plugin uses, including draft, active, paused, and disabled, then turns each one into a kanban lane with a live count next to the lane title.
3

Choose what shows on each card

Decide which rule fields appear on the front of each card. Most teams pick the rule title, the trigger label, the carrier list, and the relative updated time. Recipient details and merge tags open in a side panel without crowding the board on a laptop screen.
4

Turn on drag-and-drop writes

Flip the drag-and-drop switch and SleekView starts writing status changes back to the notification post on drop. Permissions follow WordPress capabilities, so editors can move rules between draft and active while only admins can disable rules that span the whole site.

Sample board

Sample Notification rule board

A live SleekView Kanban grouping Notification by BracketSpace rules by status, with cards showing rule title, trigger, and carrier list for each row.
Draft
18
Alert on failed Stripe webhook
trigger: webhook fail, carrier: Slack
Notify editor on new pitch
trigger: post status pitch, carrier: email
Tell sales when lead form submits
trigger: form submit, carrier: webhook
Active
84
Email customer on order processing
trigger: order processing, carrier: email
Slack engineering on plugin update
trigger: plugin updated, carrier: Slack
Notify admin on new user signup
trigger: user registered, carrier: email
Paused
9
Alert on every comment posted
paused during launch week
Notify owner on every page edit
paused: too noisy in standup
Slack ops on cron run
paused while debugging cron
Disabled
23
Email old admin on weekly digest
disabled: admin left team
Notify legacy webhook on order
disabled: endpoint retired
Slack channel on form submit
disabled: channel archived

Comparison

Default rule list vs SleekView Kanban

Default Notification rule list

  • Flat post table that lists every rule together regardless of active or disabled state
  • No visual sense of how many rules are paused or disabled right now at a glance
  • Enabling or pausing a rule requires opening each row and flipping the status setting
  • Bulk actions limit you to delete and basic edit with no card-style preview of rules
  • Mobile admins get the same dense WordPress post table with painful horizontal scroll

SleekView Kanban

  • Groups notification rules by post_status with live row counts per lane
  • Drag a card between lanes to flip a rule between active, paused, draft, and disabled
  • Card fronts surface rule title, trigger label, carrier list, and relative updated time
  • Disabled and draft rules sit in their own lanes so the active set stays clean
  • Capability-aware drops respect WordPress roles so only admins can disable site rules

Features

What SleekView Kanban gives you for Notification by BracketSpace

Native Notification field support

SleekView reads every notification rule field directly, including the trigger, carrier list, recipients, merge tags, and updated timestamp. Pick exactly which fields show on the card front, which open in a side panel, and which stay hidden but searchable from the filter bar above the board.

Drag to enable, pause, or retire

Every drop writes the new notification post status back in a single update. The trigger dispatcher and carrier registrations stay in sync, so dragging a rule into active immediately starts firing it on its trigger without a save, and dragging it into paused stops it without breaking the recipient list.

Filter by trigger, carrier, or recipient

A filter bar above the board narrows lanes by trigger, carrier, or recipient role. Saved filters are per-user, so the dev clearing webhook rules keeps a focused board while marketing can pull up only the email rules from the same notification post type.

Audience

Three teams using the Notification kanban

Admins cleaning rule libraries

Admins use the disabled lane to clear old rules that point at retired webhooks, dragging them to trash in bulk instead of opening each row to delete it one at a time.

Ops teams pausing noisy rules

Ops teams pause noisy rules in bulk before a launch by dragging them into the paused lane, then drag the same cards back into active when the launch is over and traffic is steady.

Builders shipping new rules

Builders work in the draft lane while wiring up triggers and carriers, then promote ready rules into active in one drag once the recipients and merge tags are confirmed correct.

The bigger picture

Why a kanban beats a list for notifications

Notification rules are infrastructure, not posts. Notification by BracketSpace is a powerful trigger and carrier engine, but the default rule list treats every rule the same way regardless of whether it is firing every minute, paused during a launch, or pointing at a webhook that retired last year. That works at ten rules.

It falls apart at a hundred. A kanban board fixes the shape of the data, not its presentation. Lanes show how many rules are active, paused, drafted, or disabled right now, drag-and-drop turns enable and pause into one gesture instead of a rule edit, and filters let each builder focus on the carrier or trigger they own.

The same Notification data powers a different mental model, one that surfaces dead rules pointing at dead endpoints and noisy rules firing on every comment, and turns a tangled rule library into a workspace your team can keep clean as the site grows.

Questions

Common questions about SleekView Kanban for Notification by BracketSpace

SleekView reads Notification by BracketSpace data directly from the WordPress database, so any version that writes rules to the standard custom post type works. Both the free core and the Pro extensions expose the same post type, which means the kanban renders the same way regardless of which Notification license you run.

 

Yes. The drag handler updates the same post status field that the trigger dispatcher checks before firing, so the rule starts running on its next trigger exactly as it would if an admin set the status to publish from the rule edit screen.

 

Yes. SleekView views are configuration only, so you can build one board filtered to email rules and another to Slack rules from the same notification post type. Each user picks their default board, and admins can pin shared boards to the WordPress sidebar for the whole team.

 

SleekView reads distinct status values on every load, so a new status shows up automatically as its own lane at the end of the board. You can drag it into the right position in the pipeline, assign a color, and decide which fields the lane's cards should surface, without rebuilding the view.

 

No. The drag handler updates the same post status field that every Notification add-on listens to, so any hook tied to the rule status fires exactly as it would if a builder changed the status from the rule edit screen, including custom carriers built by your own team.

 

SleekView respects WordPress capabilities, so you can require manage_options or a custom capability before a card can land in the disabled column. Builders see the lane and can scroll it, but the drop target rejects their card with an inline message instead of silently disabling a critical rule.

 

Each lane uses a virtual scroller, so a column with hundreds of cards still renders fast and stays responsive on a laptop. The lane header shows the exact count, and the filter bar at the top of the board narrows large lanes without resetting the scroll position or any cards in motion.

 

SleekView reads and writes the existing Notification post type and meta tables and never adds shadow tables for rule data. View configuration sits in its own small options table, so uninstalling SleekView leaves every rule, trigger, carrier, and recipient exactly where Notification wrote it.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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