Toolset Views is the loop builder side of Toolset. It reads the same Types schema as the Blocks plugin: custom post types from Types, wpcf-* meta fields, and relationships in toolset_associations. Views shines on the front end and supports back-end loops too, but back-end loops still mean designing a template, choosing a layout, and maintaining it alongside the content model.

SleekView gives you the admin table without the template. Every wpcf- field is available as a column, relationships from toolset_associations resolve to titles or counts inline, and intermediate post types are first-class sources. Filter by status, date, or related Type, sort by the underlying field type from the Types registry, and inline edit cells through the Toolset Types API so Access rules, Forms hooks, and conditional logic all continue to apply.

Saved views per role replace the practice of building dozens of admin-only Views just to give editors a workable column set. Toolset Views keeps owning the rich front-end loops, and SleekView owns the generic admin table on top of the same Types data. The two coexist cleanly because they read the same source of truth.

Toolset Views was designed for loops, and it does loops well. The convention of using a back-end View to give editors a workable admin column set predates plugins like SleekView, and it shows. Every new field means editing a template, every role with different needs means another View, and the admin ends up coupled to the loop builder.

The fix is to keep Toolset Views on the front end where it shines and give the admin a different tool. SleekView reads the same wpcf-* meta, the same toolset_associations table, and the same Types registry, then exposes a sortable, filterable, inline-editable table without a template in sight. Front-end Views keep rendering rich public pages.

Admin tables stop being a side project. The Types schema stays the single source of truth, and editors get an admin that matches the data model.