BuddyDrive gives BuddyPress members a personal file area with privacy controls (private, friends, group, password protected, public) and group sharing. Files land as the buddydrive-file custom post type with privacy in postmeta and mime types in standard attachment metadata. The default surface is a per-profile file area and an admin moderation queue, which is right for individual member work and wrong for understanding how members are using storage as a whole.

SleekView reads wp_posts filtered to post_type=buddydrive-file, joined with wp_postmeta for privacy and group assignment plus wp_users for display_name. Each file is one row with title, uploader, privacy level, group, mime type and upload date as real columns. Filter to private uploads for storage policy reviews. Sort by post_date for moderation triage. Filter by uploader for quota outreach.

BuddyDrive keeps owning the upload flow, privacy enforcement and the per-profile file area. The table view owns the audit surface, so the files buddydrive-file already records stop hiding inside per-profile areas and become something moderators and operators can actually query.

BuddyDrive captures something genuinely useful: per-member file storage with privacy levels and group sharing stored as buddydrive-file posts and postmeta. The default surface tucks that signal into per-profile file areas and an admin queue, which is right for individual member work and wrong for almost everything moderators, managers and operations do at the community level. SleekView reads the same buddydrive-file rows and renders them as a queryable audit table with uploader, privacy, group, mime type and upload date as real columns.

Filters stack into a single query so the privacy review, the group storage audit and the quota outreach list become one-click saved views. BuddyDrive keeps owning uploads, privacy enforcement and per-profile rendering, while moderators and operators get the per-row surface the dataset always deserved.