Both. SleekView reads Memberium tables and the status 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 Memberium membership functions, which fire the same hooks the admin uses. Any custom listener on memberium_status_changed runs exactly as if you had edited the membership from the standard Memberium admin, and ActiveCampaign tag sync is queued the same way.

Yes. Card layouts are per board. A memberships board can show email, plan, AC contact id, and renewal date. A sync queue board can show user, tag, attempt count, and last error. Each board remembers its own card template so the team does not reconfigure when switching context.

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

Add the value in Memberium the way you normally would, by adding a new state through the plugin filters or by adding a custom tag mapping. SleekView picks it up on the next board load because columns are derived from the distinct status values present on rows, not a hard coded enum.

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

Yes. Any Memberium related table with a status like column is a valid board. The sync queue table, the tag log, and the API call log all work the same way as the main memberships board does, once you point SleekView at the right table and pick a column to group on.

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