PeepSo Videos adds video uploads on top of the PeepSo community plugin, storing each upload as a row in peepso_videos with metadata covering file, size, mime, duration, and status. Each video is also attached to an activity record in peepso_activities so the wall feed knows about it, and ownership joins back to users via user_id. The default PeepSo admin shows uploads in a generic list with limited columns and no cross-member moderation queue.

SleekView reads peepso_videos directly, joins peepso_activities for the wall context and users for the owner's email, and pivots the result into a flat table. Filter by status, mime type, or upload date, sort by file size to find the heaviest assets, and group by uploader to see who is pushing the most video into the community.

Inline edits go through PeepSo's own model methods where exposed, so deleting a video also tidies the linked peepso_activities row and any cached thumbnails. Direct table writes are available for back-fills and migrations, with conflict detection on the id column. Moderation actions become a saved view, not a navigation exercise.

Communities that allow video uploads quickly accumulate moderation debt without a workspace that matches the work. PeepSo Videos handles ingestion well and the data structure itself is solid — peepso_videos with status flags, joined to peepso_activities for the wall context, joined to users for ownership. The default admin's per-profile drill-down breaks down once uploads cross a few hundred per week, because a moderator's natural unit of work is "all pending uploads across the whole community, oldest first" not "pending uploads on User A, then User B, then User C".

Storage audits face the same shape mismatch: an admin planning a CDN move needs the heaviest files surfaced regardless of who uploaded them, and a community manager hunting for spam needs top-volume uploaders surfaced regardless of which posts they appeared in. SleekView's job is to compose those views directly against the same tables PeepSo already maintains, with writes routing through the plugin's model so its cascade logic keeps working. Same database, hooks intact via the API path, dramatically less profile-by-profile clicking for the people who do the actual moderation.