No. BracketSpace Notification still owns triggers, carriers, merge tags and the queue logic that fires each rule. SleekView is a faster admin layer on top — it reads the same storage and uses the same save APIs. Disabling SleekView leaves all your rules and history untouched. Think of it as a replacement for the list screen only.

Yes. Recipient changes, carrier swaps and status toggles all run through Notification's own data layer, which means its hooks (notification/save, notification/active_changed) fire normally. Anything you have wired up — logging, audit trails, sync to staging — keeps working. SleekView is not bypassing the plugin, just giving you a better way to call into it.

Yes. The grid checks which storage format is active and reads the legacy CPT or the newer custom table transparently. If you migrate from v8 to v9, the column layout, saved views and filters carry over. Sites mid-migration with rules in both formats see them merged in the same list.

Yes. Slack, Discord, Twilio, Telegram and any other carrier extension that registers itself with Notification appears as a value in the carrier filter. Carrier-specific recipient fields (a Slack channel ID versus an email address) render correctly in the recipient column with the right formatting and validation per type.

No. Webhook URLs, API tokens and any field flagged sensitive stay masked in the grid unless the current user has the capability you configure. The mask works at render time, not just CSS, so the values do not appear in CSV exports or HTML source for users without permission.

Yes. Per-role row scoping lets you show only the notifications a given team owns — for example, security sees only auth-related triggers, editors see only post-lifecycle ones. Capability checks run on read and write, so a scoped editor cannot see or modify rules outside their slice even by URL manipulation.

Recipient strings with merge tags like {post_author_user_email} or {user_role} render the literal tag in the column with a hover preview showing the resolved value against a sample post or user. That keeps the grid scannable while still letting moderators sanity-check what a rule will actually deliver.

Yes. Select any range of rows and use the bulk action to flip status, which is useful when you need to silence a noisy carrier during an outage or enable a batch of rules after a planned maintenance window. Each change goes through Notification's normal status-change hook so audit logs and sync layers stay consistent.