Yes. The perk writes its limit configuration to gf_form_meta on each form and relies on gf_entry counts to enforce the cap. SleekView reads both, joins them, and exposes form ID, submitter, date_created, and the limit value as chartable fields.

Yes. Group a horizontal Bar by form_id on gf_entry for the current limit window, then compare against the limit value joined from gf_form_meta. The card lists every form with its current count, sorted by closeness to cap.

Group entries by created_by and filter to forms with per-user scope. The card surfaces the top submitters approaching their personal cap, so registration ops can reach out or extend the limit before legitimate signups get rejected at the wire.

Aggregations run as SELECT ... GROUP BY against indexed columns on gf_entry. Card render time scales with the cardinality of form_id or created_by, not raw row count, so even a long history of entries stays responsive when capacity ops opens the dashboard.

Cards re-query on view load and on filter change. Set a refresh interval per view if a capacity dashboard needs near-live counts during a registration peak. Idle dashboards don't poll, so a closed view doesn't add database load.

Yes. Save views and scope per WordPress role or capability. Capacity ops sees a global dashboard, registration managers see per-user caps, and editors see only the forms they own. Each user keeps their personal filters between visits.

SleekView reads the current limit value from gf_form_meta, so a mid-window change shows up on the next card refresh. Entry counts come from gf_entry as they are at query time, so the dashboard reflects the live state of the cap and the queue.

Each card exports its aggregated rows as CSV with the group-by labels and the aggregate values. Useful for sharing a per-form capacity snapshot with the campaign owner or archiving the end-of-window count for compliance and review.