Yes, the kanban reads the field records the plugin stores regardless of whether the field type was added by Checkout Field Editor itself or registered by another plugin. Custom types appear on the card as their type identifier, so a third party file upload field is just as visible as a standard text field.

Yes, when writeback is enabled, dragging a card from active to hidden updates the field's visibility through the plugin's settings store. The change is reflected on the live storefront checkout immediately, just as if you had toggled the visibility setting from the plugin's own admin screens.

Yes, the required flag is one of the metadata fields you can map onto the card front. Required fields are also collected in their own column, so you can see at a glance which fields your checkout demands and which ones are optional without scanning the storefront.

The full configuration is preserved while a field sits in the hidden column, so moving it back to active restores the exact label, type, required flag, and validation rules the field had before. Hiding is a visibility toggle, not a deletion, and there is no risk of losing field configuration during the move.

Yes, the kanban inherits the same capability checks Checkout Field Editor applies to its admin screens. An administrator can drag cards between status columns and update visibility, while a role without that capability can view the board but cannot move any cards across the columns at all.

Yes, SleekView ships with filters that scope the board to a single section. Filter to billing fields, shipping fields, or additional fields, and the visibility columns rescope to that section with the counts recalculated for just the fields that appear in that part of the checkout form.

It is a status-based grouping that includes any field marked required regardless of whether it is currently shown. That makes it a real audit of data demands, because a required field that was temporarily hidden still represents a configuration choice your privacy team should know about and document.

Per-user layout preferences are saved in WordPress user meta, so each administrator can hide columns or reorder them without affecting other admins. The Checkout Field Editor settings themselves live in the plugin's own store, so layout customizations never affect the live checkout configuration on the storefront.