Gravity Perks layers dozens of enhancements on top of Gravity Forms, but the underlying storage is still gf_entry and gf_entry_meta. Entry status remains the same four-value column Gravity Forms ships with: active, spam, trash, and the optional payment status. The default Entries screen shows that column as a filter tab at the top, so triaging means switching tabs and using bulk actions on a checkbox list.

SleekView Kanban reads gf_entry and groups by status directly, with one column per value. Card fronts pull perk-aware field values from gf_entry_meta, including Populate Anything lookups, Nested Form parent IDs, Limit Submissions counters, and any custom merge tag a perk writes. The board respects the form ID filter so a single view can cover one form or a saved set.

Dragging a card from Active to Trash calls GFAPI::update_entry_property() with the new status, which is the same path the Entries screen uses. Perks that hook into status changes, including Email Users, Entry Automation, and any custom add-on, fire exactly as they would from the standard interface.

Gravity Perks shines on the form side: smarter populating, nested submissions, submission limits, advanced conditional logic. On the entry side, all that smarts collapses back into the same Entries screen Gravity Forms has shipped for years. A reviewer triaging fifty membership signups still works through a paginated table, opens each entry for context, and uses bulk actions to move status.

The kanban view reshapes the queue around the column Gravity already maintains. Status becomes the axis, payment status sits next to it, and the perk-specific fields that explain why an entry matters move onto the card front. The drag is not a UI gimmick: it routes through GFAPI::update_entry_property() so every perk that listens to status hooks behaves as if the admin clicked from the standard screen.

The plugin keeps owning forms and perk logic. SleekView Kanban gives the resulting queue a shape that matches the way reviewers actually work.