Ultimate Member's Private Messaging extension adds messaging on top of the core usermeta-driven profile system. Conversations land in dedicated tables (commonly um_pm_conversations and um_pm_messages in installs where the extension creates its own tables, or in the configured custom tables documented by the extension), with conversation_id, sender_id, recipient_id, message, and date_sent. The profile owners come from wp_users and wp_usermeta.

The default extension admin shows conversations as a list and one-message-at-a-time review. Cross-thread audits (every message from a flagged account in the past week, or every unread message older than 30 days for cleanup) require custom SQL. Filters that combine sender profile fields (role, account_status) with message recency aren't a built-in screen.

SleekView reads the messaging tables directly, joins wp_users + wp_usermeta for sender and recipient profile data, and exposes date_sent, read_status, and per-thread message counts as proper columns. Inline edits flag messages for review or mark them deleted with conflict detection so concurrent moderator actions don't overwrite each other.

Private messages are the part of a community where bad behaviour hides. Activity feeds and forum posts get moderated quickly because they're public; one-to-one and small-thread messaging are visible to almost no one until an abuse report arrives. By then the question is always the same, what else has this account sent in the past week, and the default UM Private Messaging admin can't answer it without opening each thread.

The data is there, because every message has a sender, a recipient, a thread, and a timestamp. The gap is composition. SleekView's pivot turns those columns into a flat table where the abuse-team question (every message from this account in the past 7 days) and the moderator question (every flagged message right now across the community) become one filter each.

Joining the sender's Ultimate Member profile fields onto the message row means newly registered cohorts, suspicious account-status combinations, and freshly approved accounts in the middle of a message spike are visible without leaving the table. For any community with private messaging turned on, that's the difference between catching abuse early and finding out about it weeks later.