Yes. SleekView writes the new value back to the chosen stage field on the same record, using the same database calls the FluentCRM Automations admin uses, so any hooks, automations, or notifications already in place fire exactly as they would.

You can group by any single-value field SleekView detects on the source, including the chosen stage field, owner, priority, or a custom meta key. The dropdown in the view editor lists every available option, and switching is one click.

The card snaps back to its original column, an inline error appears on the card explaining the reason, and the underlying record is never modified. Nothing partial is written, so the source stays consistent even if multiple users drag at once.

Yes. SleekView polls the source on a configurable interval and pushes changes to every open board, so two users editing the same record from two surfaces see each other's updates within seconds without a full page reload required.

Yes. Card layouts are saved per saved view, so a rep board can show owner, value, and next-step, while a manager board of the same data shows source, age, and probability. Users switch between saved views from the SleekView header bar.

Yes. The Kanban view is a render mode on the same SleekView source, so filters, search, sort, and saved views are shared with the Table and Charts views. Switching modes never rebuilds the query, it just changes how rows are rendered.

Queries are scoped to the visible columns and limited to the page size you set, so load is comparable to the FluentCRM Automations admin list. Boards with hundreds of records use the same indexes the plugin already maintains, with no extra tables.

Yes. Each saved view has its own capability gate, so you can publish a read-only board for a wider audience and a draggable board for sales managers. SleekView respects WordPress capabilities and any custom caps your role plugin already adds.