Both. Free fields work fully and render as proper columns with sort, filter, and inline edit support. PRO fields like Repeater, Flexible Content, and Gallery render as expanded views in the table when ACF PRO is active, with row counts and summaries inline. SleekView reads whatever the registered field definitions describe.

Yes. SleekView writes through ACF's update_field() and update_sub_field() functions, so acf/save_post, acf/update_value, and field-level hooks fire as expected. Custom validation and acf/load_value filters also continue to apply, which means any saved logic you've added to a field continues to run from the table edit path.

Yes. ACF Options are first-class objects in SleekView, so a single options page can be a one-row table you edit inline. Each option becomes a column, repeaters on options pages render with row counts, and saving a cell calls ACF's options-aware update functions so the change lands in the right place in the options table.

Yes. Any post type registered with ACF or a custom post types plugin can have its own SleekView with the relevant ACF columns. The post type registration is what determines table membership; the field group registration determines which fields are available as columns. Mix and match as your model evolves.

Yes. Field values used inside ACF Blocks live in postmeta or block attributes depending on how the block is registered, and SleekView surfaces both per post. A view of pages using a particular ACF Block, with the block's field values as columns, is one saved view away.

Yes. SleekView paginates and only loads the columns you've added to the visible view, so even content models with dozens of fields stay responsive. Heavy fields like galleries and flexible content load summaries by default and only expand on demand, keeping the initial table query lean.

Both are fully supported. ACF stores term field values in termmeta and user field values in usermeta, and SleekView builds tables for taxonomies and user roles the same way it does for posts. A taxonomy view shows term meta as columns; a user view shows usermeta-backed ACF fields next to native user columns like role and last login.

ACF's bidirectional relationship features write to both sides on save. SleekView's inline edits go through update_field(), so when bidirectional logic is configured, both sides update the same way they would from the post edit screen. The view itself shows the side you queried, but you can build a second view from the other angle to verify.