Both. SleekView reads SuiteCRM 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 SuiteCRM Bridge update endpoint, which hits SuiteCRM through its REST v8 API. The plugin fires its normal record synced hooks, so any local listeners and any SuiteCRM workflow rules that key off the stage transition run exactly as they would on a manual edit in the SuiteCRM user interface.

Yes. Card layouts are per board. An opportunities board can show deal title, account, owner, revenue, and close date. 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 boards.

Yes. SleekView respects every capability check the bridge plugin registers. A user who can read but not write opportunities will see cards but the writeback only fires for users whose role matches the same checks the bridge enforces when a manual save is attempted from the admin.

Add the new stage in SuiteCRM the normal way, by editing the sales_stage_dom dropdown values. 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 stage values currently present on rows.

No. SleekView paginates cards per column rather than fetching every row. The cache table carries an index on the stage column so counts and a window of cards stay fast even on a SuiteCRM tenant with tens of thousands of opportunities flowing through the bridge over time.

Yes. Any cached SuiteCRM table with a status like column can render. Leads grouped by status, cases grouped by state, and accounts grouped by tier are common boards once you point SleekView at the right table and pick the column you want the kanban to group on.

It stays in sync because there is no separate database. SleekView reads the cached sc_opportunities rows the bridge admin reads. Writes call the bridge endpoint that talks to SuiteCRM over REST v8, so the kanban board and the SuiteCRM remote remain aligned on every change without any extra cron sync.