Yes. WP Project Manager (weDevs) uses custom tables — pm_projects, pm_tasks, pm_milestones, pm_boards, and pm_meta. SleekView reads them as first-class data sources, just like any custom table on your site.

Yes. That's the main reason teams build a SleekView for Project Manager — the default UI is project-scoped. SleekView joins pm_tasks with pm_projects so you can see every task across every project in one flat list.

SleekView writes through the plugin's API where one is exposed; otherwise it writes directly to the table with its own audit log. Status-change hooks and notification triggers fire when the API path is used.

Yes. pm_meta stores per-task and per-project metadata. SleekView pivots specific meta keys into named columns so a key like billing_status becomes a real, sortable column.

Yes. Each view in SleekView can render as table or kanban. For Project Manager that's useful when ops wants a sortable list and the design lead wants a status board, both pulling from the same pm_tasks data.

Yes. SleekView is read-and-write on the same tables but it doesn't modify the plugin or its admin UI. Default screens still work as expected; SleekView is an extra surface for teams that need flat, filterable lists.