ACF Extended itself runs on the free or PRO version of ACF for most modules, with some PRO-only paths. SleekView Charts reads whatever ACF Extended writes, so it works the same way regardless of which ACF tier is installed underneath.

Yes. Dynamic blocks store their block name and field values per post, and SleekView reads both. A Pie or Bar card grouped by block name returns usage across the site, and clicking a slice opens the underlying posts in the table.

ACF Extended writes submissions into a custom post type or option storage depending on how the form is configured. SleekView reads the configured storage, so the chart cards count exactly the submissions ACF Extended itself records, with no separate database.

Yes. The Performance module records flush events when the field group registry changes. Group by the flush date with an Area or Line card to trend how often the model actually changes in production, which is useful for measuring deploy hygiene.

Yes. Edits made from the table that backs the chart go through ACF's update_field() and the ACF Extended save paths, so module-specific hooks fire just like they do in the standard editor. Custom validation continues to apply.

Yes. ACF Extended's dynamic post types are real registered post types, so SleekView treats them like any other CPT. A dashboard can group, count and trend rows from a dynamic post type alongside rows from a hand-registered one.

Yes. Field type extensions like Advanced Link, Block Types and Image Selector store their values in postmeta or term/usermeta. SleekView surfaces those values for both columns and chart dimensions, so a Pie or Bar can group by an extended field.

Yes. Each saved dashboard is gated by WordPress capability and can be exposed to specific roles. Form ops can see the form submissions dashboard, developers can see the modules dashboard, content editors can see only the block usage one.