Toolset Types Pro is the schema engine of Toolset. It registers custom post types, wpcf- custom fields in wp_postmeta, and post relationships in toolset_associations together with toolset_relationships for the definitions. The default Types admin uses WordPress's list screen with a handful of opt-in columns, which works for small models but stops scaling when there are dozens of fields per type or several relationships per row.

SleekView reads the Types Pro registry directly. Every wpcf- field becomes a sortable, filterable column with the correct underlying SQL type from the field definition. Relationships resolve to titles or counts inline, and intermediate post types for many-to-many relationships are first-class sources you can open as their own SleekView. Repeating field groups expand per row through the Types repeating field API.

Inline edits route through Toolset Types Pro's update API, so any Forms-side validation, Access permissions, and conditional logic continue to fire on every cell save. Saved views per role replace the practice of registering one-off admin pages for each Type, and SleekView coexists cleanly with Toolset Views, Forms, Blocks, and Access because it sits on top of the same schema instead of replacing it.

Toolset Types Pro defines a clean content model: post types, custom fields with a known prefix, and relationships in their own table. The schema is one of the most disciplined in the WordPress plugin ecosystem. The default admin doesn't live up to that discipline.

Custom fields aren't shown as columns by default, relationships aren't visible without a View, and repeating field groups are invisible on the listing. Teams end up registering one-off admin pages or building admin-only Views to compensate, which couples the admin to either custom PHP or to the loop builder. SleekView gives the same schema a generic, sortable, filterable, inline-editable admin table.

Every wpcf- field can become a column. Every relationship resolves inline. Every repeating field group expands per row.

Edits route through the Types Pro update API so Forms hooks, Access rules, and conditional logic stay in charge. The admin finally catches up to the schema, and developers stop writing list-table code for every new model.