SleekView for GravityView
SleekView reads gf_entry, gf_entry_meta and the gravityview post type, surfacing approval state, view, form and approval timestamp as real columns so directory editors and moderators see the queue as a list rather than paging through a per-view approval screen.
♾️ Lifetime License available
GravityView publishes entries. The moderation queue needs a real table.
GravityView turns Gravity Forms entries into front-end directories, member listings, business catalogues and resource libraries. Each view is a WordPress post in the gravityview post type, pointing at one or more Gravity Forms forms and applying its own template, filters and approval rules. Entries flow from gf_entry into the configured layout, with approval state stamped onto gf_entry_meta when the approval workflow is enabled.
The default GravityView admin is excellent for editing a single view and reviewing one entry at a time. It is less useful for cross-view questions like "how many entries are unapproved right now", "which entries are starred for follow-up" or "which view is publishing the most fresh content". Those answers live in gf_entry plus the gravityview meta and never make it to a list view.
SleekView reads gf_entry, the gravityview post type and the GravityView approval meta keys. Approval state, starred flag, view, form and approval timestamp sit as real columns next to entry ID and submitter. Sort by approval state, filter to unapproved across every view, bulk-approve a clean cohort, or export the audit list to CSV.
Workflow
How SleekView reads GravityView data
Pick the entry source
Compose the column set
Save and scope the view
Edit inline or export
Sample columns
A typical GravityView entries table
gf_entry + gf_entry_meta (is_approved, is_starred) + wp_posts (post_type = gravityview)
| Entry | Submitter | View | Approval | Starred | Approved at |
|---|---|---|---|---|---|
| 4821 | Sara Klein | Member directory | Approved | Yes | May 14 |
| 4820 | Omar Patel | Business catalogue | Unapproved | No | — |
| 4819 | Lina Schmid | Member directory | Disapproved | No | May 13 |
| 4818 | Tom Jiang | Resource library | Approved | No | May 12 |
| 4817 | Petra Novak | Business catalogue | Unapproved | Yes | — |
Comparison
Default GravityView admin vs SleekView
Default GravityView admin
- Approval queue surfaces per view, not as a single cross-view list
- Approval state visible per entry, not as a sortable column across views
- Starred flag set per entry, no filter across the directory programme
- Bulk approve limited to a single view at a time
- No saved per-role view for editors, moderators or owners
SleekView
- Read directly from gf_entry joined with GravityView approval meta and the gravityview post type
- Approval state, starred flag, view and approval timestamp as sortable, filterable columns
- Bulk-approve across every view in one pass
- Save filtered views per role ("Unapproved queue", "Starred for follow-up")
- Filters carry between the table view and the chart view on gf_entry
Features
What SleekView gives you for GravityView
Approval meta as real columns
Surface is_approved, is_starred and the approval timestamp alongside entry ID, submitter and view. The moderation queue moves from a per-view screen to a cross-view list.
Cross-view backlog filter
Filter to unapproved across every GravityView and the table reveals the full moderation backlog. Bulk-approve a clean cohort in one pass.
Audit moderator throughput
Surface the moderator who toggled approval as a column and sort by approval timestamp. Confirms the team is keeping pace with submission volume.
Audience
Who uses SleekView for GravityView
Directory editors
Anchor a weekly review on approved entries per view. Spot the directory that has not gained a new entry in a month before traffic notices stale listings.
Moderators
Filter to unapproved across every view and clear the backlog in one place rather than view by view.
Site owners
Track view post_status and creation cadence across the gravityview post type. Confirm the directory programme is growing in line with editorial planning.
The bigger picture
Why GravityView needs a moderation table
GravityView turns Gravity Forms into a content product, member directory or business catalogue. The underlying gf_entry data is rich, the approval workflow stamps clean meta and the gravityview post type makes every view discoverable. The default admin does an excellent job at editing a single view, but it offers no cross-view list of the moderation backlog.
Approval backlog across views, starred entries for follow-up, moderator throughput and per-view publishing volume are the questions a programme lead asks, and the default UI cannot answer them without manual filtering inside each view. Reading gf_entry plus the GravityView meta as a real table changes the posture from "approve the next entry" to "run the directory as a programme". A growing unapproved cohort shows up on a sort by approval state before moderators feel buried.
A quiet view shows up in a filter for entries this month before traffic stalls. Same data the front-end views render, finally available as the table the directory team always needed.
Questions
Common questions about SleekView for GravityView
The Gravity Forms gf_entry and gf_entry_meta tables plus the gravityview post type and its configuration meta. No data is duplicated, the table runs against the same tables GravityView already uses to power front-end views.
Yes. Approval columns depend on the is_approved meta GravityView writes, so they only appear when the approval workflow is enabled. Per-view entry-count views, view-status filters and entry-cadence sorts work regardless of approval configuration.
Yes. Approval edits flow through the GravityView API so notifications and any custom approval hooks still fire. Bulk-approving a filtered cohort works the same as approving a single entry inside a view.
Yes. Filters applied at the GravityView level are mirrored when the table reads gf_entry through the view_id grouping. The table reflects the same entries the front-end view publishes, not the underlying form before filtering.
No. Gravity Forms indexes gf_entry on form_id, status and date_created, and SleekView uses those indexes. Directory sites with hundreds of thousands of entries render the table in well under a second.
Yes. Views configured with multiple forms contribute their entries to the same view grouping. The table reflects the combined directory rather than splitting it across the underlying forms.
Yes. Filter to entries where is_starred is true and sort by date. Useful for moderators who use the starred flag as a personal review marker before final approval.
Yes. Each saved SleekView is scoped by WordPress capability. Moderators see the approval queue while directory leads see the view-audit table, each with its own filter presets and exports.
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