Both. SleekView reads Cimy User Extra Fields tables and the cimy_activation 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 Cimy activation functions, which fire the same hooks the admin uses, including welcome emails. Any custom listener you have on cimy_uef_activated or related events runs exactly as if you had activated the user from the standard WordPress user profile screen.

Yes. Card layouts are per board. Your activation board can show email, role, and registration date. A custom field audit board can show the field value, the user, and the cohort. Each board remembers its own card template so the team does not reconfigure when switching context.

Yes. SleekView respects every WordPress capability check Cimy registers. A user who can view but not edit other users can drag a card to inspect details, but the writeback only fires for users with the same capabilities the user edit screen would enforce on a manual save.

Add the value in Cimy the way you normally would, by adding a new activation state through the plugin filters or a custom user meta key. SleekView picks it up on the next board load because columns are derived from the distinct meta values present, not from a hard coded list.

No. SleekView paginates cards per column instead of loading every user up front. The board fetches counts via an indexed meta query, and each column loads a window of cards on demand, so even a site with hundreds of thousands of users stays responsive on standard hosting setups.

Yes. Any Cimy related table with a status like column is a valid board. The custom field data table can be visualized too, grouped by any field that has a finite set of values, so admins can audit field completeness across the entire membership at one glance.

It stays in sync because there is no separate database. SleekView reads the same wp_cimy_uef_data table and the user meta the Cimy admin reads. Changes on the kanban appear in the user list immediately, and edits from the admin appear on the next board refresh.