The Gravity Forms User Registration add-on creates a WordPress user from a form submission, with optional double opt-in activation through a pending state stored in wp_signups. Entry meta records the activation status, the activation key, and the linked user_id once activated. The default Gravity entries grid shows the entry but hides whether the user was created, is still pending email activation, or was rejected during a manual approval step.

SleekView reads wp_gf_entry directly, joins to wp_gf_entry_meta, and surfaces the User Registration meta keys as groupable fields. The natural one is activation status with Pending, Activated, Approved, and Rejected columns. You can also group by the role assigned, by the form-specific custom approval stage, or by linked user properties like role count or first login date pulled from the WordPress user table.

Dragging a card writes the new value through GFAPI::update_entry and fires gform_post_update_entry, which the User Registration add-on listens to for downstream user lifecycle actions like role updates and welcome email triggers. Rejected registrations are filtered out of active activation boards by default but can be exposed on a moderation audit board so admins can see rejection patterns and reach out to legitimate registrants who got mistakenly rejected.

The Gravity Forms User Registration add-on is excellent at turning form submissions into WordPress users, but its admin treats every registration as a row in the standard Gravity entries grid with no visibility into where each user is in the activation lifecycle. That works when registrations are occasional. It stops working the moment you have a real signup flow with double opt-in confirmation, manual approval steps, and auto-rejection rules for spam profiles, all running in parallel for dozens of registrations a day.

A kanban board fixes the part the add-on was never designed to fix: activation lifecycle visibility. Each column shows how many registrations are in each state, so admins can spot when activation emails are not converting or when the moderation queue is backing up. Status changes happen with a drag instead of three clicks per entry, which compounds quickly once you are processing hundreds of registrations a week.

Because every column maps back to real User Registration meta on the entry, the board is not a parallel system that drifts. The end result is a Gravity admin that finally matches how user onboarding teams actually work.