Both. SleekView reads Vtiger WP Bridge tables and the sales_stage column at the database level, so whichever tier you run the board still builds. Paid add-ons that add custom fields or extra status values are picked up automatically because SleekView scans the live schema on render.

SleekView calls the Vtiger WP Bridge update endpoint, which talks to Vtiger over its REST API. The plugin fires its normal record updated hooks, so any local listeners and any Vtiger workflow rules that key off the stage change run exactly as they would on a manual edit inside the Vtiger user interface.

Yes. Card layouts are per board. A potentials board can show deal title, account, owner, and amount. A leads board can show contact, source, status, and last activity. Each board remembers its own card template so the team does not reconfigure when switching contexts.

Yes. SleekView respects every capability check the bridge plugin registers. A staff user who can view but not update records will see the cards but the writeback only fires for users whose role matches the same checks the bridge enforces on a manual save.

Add the new stage in Vtiger the way you normally would, by editing the picklist for leadstatus or sales_stage. The bridge syncs the new value into the local cache, and SleekView picks it up on the next board load because columns are derived from the distinct values present.

No. SleekView paginates cards per column instead of fetching every row at once. The cache table is indexed on the stage column, so counts and windows of cards stay fast even on a Vtiger account with tens of thousands of leads and potentials carried in the bridge.

Yes. Any cached Vtiger table the bridge maintains can render. Leads and potentials are the common boards, but accounts, contacts, and quotes work the same way once you point SleekView at the right table and choose the column you want to group the cards on.

It stays in sync because there is no separate database. SleekView reads the same cached vt_leads and vt_potentials rows the bridge admin reads. Writes call the bridge API the plugin already uses, so the kanban board and the Vtiger remote remain aligned on every change.