SleekView reads widget data directly from the WordPress database, so any edition that writes its widgets and meta to the standard tables works. Both the free AAPF build and the premium AAPF Pro release expose the same schema, which means the kanban renders the same way regardless of which BeRocket license is currently active on the store.

Yes. A drop writes the new widget_status back to the same row the storefront reads on the next page render, so a widget moved into the active lane shows up on the linked category landing page within seconds. BeRocket's own caching layer flushes affected URLs so shoppers see the new filter immediately.

Yes. SleekView views are configuration only, so you can build one board filtered to women's apparel widgets and another to home goods filters from the same BeRocket table. Each user picks their default board, and admins can pin shared boards to the WordPress sidebar for the whole merchandising team.

SleekView reads distinct status values on every load, so a new state shows up automatically as its own lane at the right edge of the board. You can rename, recolor, or reorder lanes from the view config without touching the BeRocket AAPF settings, and any widgets already in the new state stay live and visible.

Yes. Drag-and-drop drops are gated by the same capability checks that protect the WooCommerce settings screen. Merchandising leads can move widgets into active, while staff with restricted roles see read-only cards on the active lane until their permissions are raised by an admin on the WordPress side.

Yes. Each card opens a side panel that pulls the target shop page, the linked taxonomy and attribute, the active and scheduled windows, and the last-edited user. A merchandiser can audit a widget end to end from the panel without jumping to the BeRocket AAPF settings screen in a separate browser tab.

Yes. Every drop records the user, the previous widget state, the new state, the affected widget, the linked taxonomy, and the timestamp into the SleekView change log. A merchandising lead can export the log as CSV at any time, which is much faster than reading raw widget revisions in the WordPress database directly.

No. SleekView lazy-loads cards per lane and paginates each column server-side, so the initial render only fetches the rows currently on screen. Stores with tens of thousands of widgets still see a board that opens in under a second, and drag-and-drop updates use single-row writes that stay fast at any catalog size.