Both. SleekView reads Salesflare for WordPress tables and the stage_id 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 Salesflare connector update endpoint, which talks to Salesflare through its REST API. The plugin fires its normal opportunity synced hooks, so any local listeners and any Salesflare workflow automations that key off the stage transition run exactly as they would on a manual edit inside Salesflare.

Yes. Card layouts are per board. An opportunities board can show deal title, account, owner, value, and close date. An accounts board can show name, tier, owner, 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 connector 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 connector enforces when a manual save is attempted from its admin.

Add the new stage in Salesflare the normal way, by editing the pipeline settings. The connector syncs the new stage into the local cache, and SleekView picks it up on the next board load because columns come from the distinct stage values currently on rows in the cache.

No. SleekView paginates cards per column rather than fetching every row at once. The cache carries an index on the stage column so counts and a window of cards stay fast even on a Salesflare account with tens of thousands of opportunities running through the connector each year.

Yes. Any cached Salesflare table with a status like column can render. Accounts grouped by tier, contacts grouped by lifecycle, and tasks grouped by status 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 sf_opportunities rows the connector reads. Writes call the connector endpoint that talks to Salesflare REST, so the kanban board and the Salesflare remote stay aligned without extra cron sync.