GravityView renders Gravity Forms entries as searchable, sortable, filterable front-end Views without custom query code. Part of the GravityKit product suite alongside GravityActions and GravityBoard.
When to use
- Displaying Gravity Forms entries on the front-end (staff directories, portfolios, listings)
- Building searchable/filterable entry displays
- Setting up entry approval workflows
- Creating edit-entry forms for front-end user editing
- Restricting views by role or entry ownership
- Building admin workflows with automated classification
Official documentation
GravityKit ecosystem
| Product | Purpose |
|---|---|
| GravityView | Display entries as Views (lists, tables, maps, cards) |
| GravityView Pro | Extended layouts: maps, tables, ratings, magic links |
| GravityActions | Bulk-update, bulk-email thousands of entries at once |
| GravityBoard | Kanban board view for entries with columns and voting |
| WordPress MCP | Surgical block-level Gutenberg editing for AI assistants |
- Account: https://account.gravitykit.com
- GitHub org: https://github.com/GravityKit
- Developer docs (hooks, Foundation, 37 products): https://www.gravitykit.dev/
Procedure
1) Install
GravityView is a premium plugin. Download from your GravityKit account and install:
wp plugin install gravityview.zip --activate
wp plugin install gravityview-datatables.zip --activate # optional table layout
Or via SatisPress/Composer:
"satispress/gravityview": "*"
2) Create a View
- Views → New View
- Select the Gravity Form to pull entries from
- Choose a layout (Table, List, DataTables, Map)
- Add fields to the Multiple Entries layout (directory view)
- Add fields to the Single Entry layout (detail page)
- Configure View Settings (sorting, pagination, entry ownership)
3) Restrict by ownership and role
View Settings → Show only entries created by the current user: ✓
View Settings → Required Capability: gravityview_view_entries
// Prevent metadata exposure in public views
add_filter('gravityview/fields/custom/content_after', function($content, $field) {
if (!is_user_logged_in() && in_array($field->ID, ['internal_notes', 'api_key'])) {
return '—';
}
return $content;
}, 10, 2);
4) Entry approval workflow
- Add Approval field to your View layout
- Configure: View Settings → Approval Status → Approved only
- Gravity Connect can auto-classify submissions:
Gravity Connect Feed → classify "Flagged" →
GravityView filter: {Approval Status} = Flagged →
Admin-only view for review
5) Edit entry (front-end editing)
- Views → Edit → add fields to Edit Entry layout
- Embed with shortcode:
[gravityview id="1" context="edit"] - Set capability: View Settings → User Edit → "Own entries only"
6) Shortcodes
[gravityview id="1"] # basic view
[gravityview id="1" page_size="20"] # paginated
[gravityview id="1" search_field="2"] # pre-filtered by field 2
[gravityview id="1" context="single" entry_id="42"] # single entry
7) MCP prototyping
Feed your GravityView structure to an LLM to generate custom layout HTML:
// Export view field config for LLM context
$view_fields = get_post_meta(get_the_ID(), '_gravityview_directory_fields', true);
echo json_encode($view_fields, JSON_PRETTY_PRINT);
Security
- Always apply entry ownership restrictions on public-facing Views
- Never expose sensitive field IDs in public shortcodes
- Use Roles and Capabilities settings to gate admin-only views
- See
wp-gravity-stack → references/security.mdfor the full audit script
References
wp-gravity-formsskill — forms and entries that feed Viewswp-gravity-connectskill — AI classification feeding GravityView filters