SendGrid (now Twilio SendGrid) deprecated its first-party WordPress plugin in 2021. Many sites still run the closed snapshot, but the bigger population has migrated the same API key into FluentSMTP, WP Mail SMTP, or Post SMTP with SendGrid as the chosen transport. The result is a network where SendGrid config is everywhere and nowhere: every site has it, but each one stores it under a different option key shape. SleekView matches the known shapes, normalises them, and presents one comparable table.

The columns ops care about are sender hygiene (from-name, from-address), transport (API vs SMTP), and category tagging. Sites still using the WordPress default sender of wordpress@blog are deliverability time bombs because the domain rarely matches a verified SPF record. The closed plugin originally exposed a category field that maps directly onto SendGrid's Activity Feed filters, and many networks set it once and never audit it. SleekView surfaces those category strings as a column so a marketing team can confirm every site reports under the right tag.

Bulk API-key rotation is the other recurring pain. After a security event, swapping the SendGrid key across forty client sites used to mean forty admin sessions or a custom WP-CLI script per SMTP plugin shape. SleekView treats the key as one column across the audit, masked by default, and lets capability-gated admins inline-edit it for the rows in scope. The Activity Feed in SendGrid then confirms whether the new key is actually in use within minutes.

When a vendor closes a plugin, the configuration it left behind doesn't get any easier to manage; it gets harder, because the natural answer (use the official UI) is no longer available. SendGrid's case is unusually broad: the closed plugin still functions on the sites that never updated, and the modern SMTP-front-end ecosystem each persists SendGrid config under different option keys. A multisite network running SendGrid through a mix of those plugins ends up with a fragmented configuration story where every audit involves remembering which plugin holds the key on which subsite.

The default-sender problem compounds the fragmentation: any subsite that never set a custom from-address sends as wordpress@blog, which fails SPF alignment and quietly tanks deliverability. The category strings, when set, are the only WP-side breadcrumbs linking a send back to a campaign in the SendGrid Activity Feed. SleekView treats this fragmentation as the actual problem to solve.

Detect every shape, normalise it, and let one team look at the whole network through one schema.