BuddyPress Followers adds Twitter-style asymmetric follows on top of BuddyPress, storing each relationship in the bp_follow table with leader_id, follower_id and date_recorded columns. The default surface is a per-profile widget showing one member's followers and followings, which is right for landing on a single profile and wrong for understanding the community graph as a whole.

SleekView reads bp_follow joined with the BuddyPress users table and renders the relationships as a sortable audit table. Filter to follows recorded in the last 30 days to track onboarding momentum. Sort by leader display_name to triage abuse reports. Group rows by member_type to see which segments are driving the graph. The same dataset the chart view aggregates becomes a row-level surface for community managers, moderators and ambassador programs.

The plugin keeps owning follow buttons, notifications and graph integrity. The table view owns the audit surface, so the relationships BuddyPress Followers already records stop hiding inside per-profile screens and become something community ops can actually query.

BuddyPress Followers captures a directed graph of who pays attention to whom inside the community, written one row at a time into bp_follow with the people and timestamps already attached. The default surface tucks that signal into per-profile widgets, which is right for opening one member and wrong for almost everything community ops actually does with follow data. SleekView reads the same bp_follow rows and renders them as a queryable audit table with leader, follower, member_type on both sides and date_recorded.

Filters stack into a single query so the recent-follows audit, the cross-segment cohort and the per-leader outreach list become one-click views rather than profile crawls. The plugin keeps owning the follow buttons, notifications and graph integrity, while community managers get the per-row surface the dataset always deserved.