Yes. SleekView supports plugins that use their own database tables. Pick connections_entry as the source table, configure the joins for address and phone, and the board reads the plugin's data directly. Status changes go through the plugin's cn_process_status hook so the standard write path runs, including moderation logs and email notifications.

Connections stores address, phone, email, and link fields in separate related tables keyed by entry ID. SleekView joins the primary address and primary phone (marked with the preferred flag the plugin sets) onto each entry, exposing city, region, country, and phone number as card fields. You pick which to display in the card face.

SleekView writes a featured key into the entry's options JSON blob, which is the same place the plugin's own Featured toggle stores the flag. The Connections frontend templates immediately treat the entry as featured, applying the featured badge, sorting it to the top of category pages, and including it in any featured-only shortcodes that the directory site uses.

Yes. Unlisted is a soft-archive status the plugin already supports. Entries in that state are invisible to the public frontend regardless of the kanban configuration, and SleekView only shows the column to users with the connections_manage capability. You can hide the column entirely from the board UI if your moderators only need to work in Pending and Approved.

Yes. Because every status change calls cn_process_status, the plugin writes the same log entry it writes for a manual moderation action: who changed the status, the previous value, and the new value. That entry shows in the standard Connections log screen and in any third-party log aggregator that listens for the cn_process_status action.

Yes. SleekView reads the plugin's category taxonomy and entry type (individual, organization, family) as filterable card fields. Moderators can pin the board to one category, one entry type, or both, and the filter persists per user. Combined with grouping by status, you get a focused moderation view per category without ever leaving the kanban.

Yes. SleekView honors the connections_view_entry_moderated, connections_edit_entry, and connections_manage capabilities the plugin already uses. Users without permission to change a status see the cards but the drag handle is disabled. Combined with the plugin's role separation between viewers and managers, the board enforces exactly the same access rules as the standard admin moderation screen.

Yes. The SleekView filter bar accepts the same category taxonomy filters the Connections frontend uses, plus address fields like city and region. You can pin a board to one chamber chapter, one industry, or one membership tier, and save the configuration so each moderator opens straight to their own scope without redoing the filters every login.