BuddyPress Private Messaging stores messages across three tables: bp_messages_messages (one row per message with sender_id, thread_id, subject, body and date_sent), bp_messages_recipients (recipient rows per thread with unread_count and is_deleted) and bp_messages_meta. The default admin barely surfaces any of it, so cross-thread audits for abuse reports, response-time review and top-sender outreach all currently require direct SQL or a spreadsheet export.

SleekView reads the three tables joined and renders the messaging stream as a queryable audit table. Filter to messages from a flagged sender for an abuse review. Filter to threads where unread_count > 0 for older than seven days to surface unresponded inbound. Sort by sender_id to triage moderation review. The same data the chart view aggregates becomes a row-level surface for moderation, support and community management.

The plugin keeps owning send, receive, threading and notifications. The table view owns the audit surface, so the data BuddyPress already stores stops requiring raw SQL and becomes something moderation can actually filter on.

Private messaging is one of the highest-signal datasets in any BuddyPress community: who is talking to whom, how often, when and whether the recipient has actually read the inbound. The default admin renders that as per-thread screens, which is right for one investigation and wrong for understanding messaging at the cohort level at all. SleekView reads the three bp_messages tables joined and renders them as a queryable audit table with both display_names, thread_id, unread state and date_sent.

Filters stack into a single query so the abuse-review queue, the unresponded inbound and the per-user audit become one-click views rather than ad-hoc SQL. The plugin keeps owning send, receive and notifications, while moderation and support get the per-row surface the dataset always deserved.