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

Yes. Card layouts are per board. A leads board can show lead title, person, company, value, and close date. A people board can show name, lifecycle, 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 leads 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 Nutshell the normal way, by editing the stageset on the pipeline. 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 Nutshell account with tens of thousands of leads flowing through the connector each year of use.

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