SleekView for BuddyMeet
BuddyMeet stores each meeting as a custom post linked to a BuddyPress group, with scheduled time, host and meeting type in post meta. SleekView reads those posts joined with bp_groups so community managers see every call across every group as a single sortable, filterable workspace instead of one tab per group.
♾️ Lifetime License available
Each group has a meeting tab, the community has no shared table
BuddyMeet adds a Jitsi-powered video meeting tab to each BuddyPress (and BuddyBoss) group, storing each meeting as a custom post (post_type buddymeet_meeting or similar) linked to a group_id, with post meta for scheduled time, host user_id and meeting type (instant, scheduled or recurring). The default surface is the per-group tab, which is the right place to start a call and the wrong place to audit activity across the community.
SleekView reads the BuddyMeet meeting posts joined with bp_groups for group name, status and member count, then renders the result as a sortable, filterable table. Columns expose meeting_id, group name, host display name, meeting type, scheduled time and post_date together. A community manager sorts by group, filters to scheduled-only or to a specific group admin, and exports the filtered cohort to CSV for a monthly community report.
Filters carry between the audit table and the dashboard chart cards, so a public-groups-only filter or a last-30-days slice narrows both surfaces. Status changes and scheduled-time edits route through the BuddyMeet data layer where supported, so any group-side hooks the plugin fires keep firing.
Workflow
How SleekView reads your BuddyMeet meetings
Connect the meeting post type
Compose the column set
Save and scope the view
Edit inline and export
Sample columns
A typical BuddyMeet meetings view
buddymeet_meeting post type + wp_bp_groups
| Meeting | Group | Host | Type | Scheduled | Status |
|---|---|---|---|---|---|
| #4821 Onboarding call | Welcome circle | Alex Reiter | Scheduled | May 14, 10:00 | Confirmed |
| #4822 Office hours | Pro members | Ria Patel | Recurring | May 15, 16:00 | Confirmed |
| #4823 Quick sync | Design crew | Tom Bailey | Instant | — | Ended |
| #4824 Member AMA | Founders lounge | Mia Brewer | Scheduled | May 16, 18:00 | Pending host |
| #4825 Coaching call | Mentor pod | Sam Ortiz | Scheduled | May 17, 09:30 | Confirmed |
Comparison
Default BuddyMeet group tab vs SleekView
Default BuddyMeet group tab
- Meeting list lives inside each group tab, never aggregated across the community
- No cross-group sort by host, type or scheduled time on a single screen
- Recurring vs instant vs scheduled mix isn't filterable on one cohort
- Bulk reschedule or bulk host reassign requires opening each group separately
- No saved per-role view for community manager, group admin or platform lead
SleekView
- Read directly from the BuddyMeet meeting post type and join bp_groups for group context
- Pivot post meta (scheduled_time, host_user_id, meeting_type) into typed columns
- Filter by group, host, type or scheduled-time window on one table
- Inline-edit host and scheduled_time across many meetings in a single pass
- Save filtered views per role ("Scheduled this week", "Top-hosting groups")
Features
What SleekView gives you for BuddyMeet
Every group meeting in one table
Replace per-group meeting tabs with a single sortable table of meeting_id, group name, host, type and scheduled_time across the entire BuddyPress install.
Host and group columns joined
Join the BuddyMeet post type with bp_groups and user_meta so the host display name and group name appear directly in the row, no manual cross-reference.
Saved per-role workspaces
Save a community-manager view, a group-admin view and a platform-lead view from the same dataset, each with its own column set and capability gate.
Audience
Who uses SleekView for BuddyMeet
Community managers
Audit every meeting across every group, identify hosting-active groups for outreach and reassign hosts when a group lead steps back, all from one table.
Group program leads
Filter to scheduled meetings in the next 7 days for an upcoming-events digest, or to top-hosting groups for spotlight features and case-study selection.
Platform admins
Spot meetings missing a host or with a stale scheduled_time, bulk fix them inline and export the filtered cohort for moderation or quarterly platform reviews.
The bigger picture
Why community video data deserves a table, not a per-group tab
BuddyMeet records the data that actually answers community-management questions: which groups are running calls, how often, scheduled or instant, and by whom. The default per-group tab is the right place to start a meeting and the wrong place to do almost anything else with the data. A table that joins the meeting post type with bp_groups and user_meta turns scattered tabs into one filterable workspace, where a community manager sorts by group, filters to scheduled-only and exports the cohort for a monthly report in one pass.
Same BuddyMeet posts, same scheduled-time meta, completely different operational posture. The table renders what the plugin already writes as a queryable surface, which is the difference between knowing groups have video and running the community programme from real data.
Questions
Common questions about SleekView for BuddyMeet
The BuddyMeet meeting post type and its post meta, joined with bp_groups for group name, status and member count, and with user_meta for host display name. No new tracker is added and no Jitsi-side data is required.
Yes. BuddyMeet supports both BuddyPress and BuddyBoss, and BuddyBoss uses the same bp_groups schema. The same table works on either platform without configuration changes.
Yes. group_id, host_user_id and meeting_type are all filterable columns. Common slices include 'public groups only', 'scheduled meetings in the next 7 days' or 'all meetings hosted by a specific group admin'.
Yes, where the BuddyMeet data layer supports it. Edits flow through the same CRUD path BuddyMeet uses, so any group-side hooks the plugin fires on host change or schedule change keep firing.
Yes. The table view and the chart view share the dataset, so a public-groups-only filter or a last-30-days slice narrows both surfaces. Community managers pivot between audit and summary without rebuilding filters.
Yes. SleekView views can be private to a user or shared with specific roles. A common setup: a manager-only audit view, a group-admin-only hosting view and a read-only stakeholder snapshot for platform admins.
No. Calls still run through BuddyMeet and Jitsi exactly as before. SleekView only renders the meeting metadata BuddyMeet already writes to WordPress as a queryable, editable table.
Yes. Any filtered cohort exports as CSV with meeting_id, group name, host, meeting_type, scheduled_time and post_date columns. Useful for community reports, quarterly reviews and ad-hoc moderation audits.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout