Yes. Form Connector writes a parent-entry reference to gf_entry_meta on connected child submissions, alongside Gravity Flow's own workflow_step and workflow_step_status meta. SleekView reads all of them and exposes them as group-by and aggregation options on gf_entry.

Yes. Group gf_entry by workflow_step regardless of source form, then filter the view to the linked forms you care about. A single Bar then shows step volume across every form in the connector chain.

Use the difference between date_updated when the step completes and date_created on the entry as a derived column. Average it across the step group to surface bottlenecks, or use Maximum to find the slowest individual entries waiting on action.

Aggregations run as SELECT ... GROUP BY against indexed columns on gf_entry and the related gf_entry_meta. Card render time scales with step cardinality, not raw row count, so even a long workflow history stays responsive on a busy approvals dashboard.

Yes. Gravity Flow stores the current assignee in entry meta. Filter the view to a single assignee user ID and every card scopes to their personal workload, then save the view per-role so the approver lands on it on every visit.

Yes. Save views and scope per WordPress role or capability. Workflow managers see global throughput, approvers see their queue, and editors see only the forms they own. Each user keeps their personal filters between visits.

SleekView counts entries that actually carry the new workflow_step value, so older submissions before the step existed don't pollute the totals. Filter to the activation date to compare the new step's throughput against the rest of the workflow.

Each card exports its aggregated rows as CSV with the group-by labels and the aggregate values. Useful for sharing per-step throughput with the workflow owner, archiving the monthly approval volume, or feeding the chain's timing into a separate report.