Both. SleekView reads Super Socializer tables and the ss_link_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 Super Socializer disconnect and rebind functions, which fire the same hooks the admin uses on a manual link change. Any custom listener you have on the_champ_link_changed runs exactly as if you had unlinked the provider from the standard user profile screen.

Yes. Card layouts are per board. A links board can show email, provider, last login, and provider id. A provider mix board can show provider name, user count, and last activity. Each board remembers its own card template so the team does not reconfigure when switching contexts.

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

Add the value in Super Socializer the way you normally would, by adding a new link state through the plugin filters. SleekView picks it up on the next board load because columns are derived from the distinct meta values present on rows, not from a hard coded enum at all.

No. SleekView paginates cards per column instead of loading every link 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 social links stays responsive on standard hosting.

Yes. Any Super Socializer related table with a status like column is a valid board. The social comment table, the share counter rows, and any custom user meta tables the plugin adds work the same way as the main user links board does on the social login surface.

It stays in sync because there is no separate database. SleekView reads the same Super Socializer user meta the admin reads. Changes on the kanban appear in the per user provider list immediately, and edits from the admin appear on the next board refresh without cron sync.