Primarily asana_tasks for the row per card and asana_sections plus asana_users for grouping and display labels. asana_projects is joined when you scope the board to one project. SleekView only reads tables the plugin already maintains, it does not call the Asana API itself.

Yes. Any column on asana_tasks is a valid grouping field. Common picks are completed for a Doing vs Done board, assignee_gid for a per-person board, or a custom field synced from Asana. Distinct values become the column titles in the order SleekView finds them.

SleekView writes the new value into the grouping column on asana_tasks and fires the plugin write hook. The next sync push sends the change to Asana over the API. Until that push runs the card stays in the new column locally so the team is not blocked by API latency.

The local table updates immediately so the board reflects the change without a reload. The push to Asana happens on the plugin sync schedule, which defaults to every few minutes. If you need instant pushes, point the plugin sync at a manual trigger and call it from a SleekView post-drop hook.

Apply a SleekView filter on project_gid or on a tag column before grouping. The filter narrows the rows the board considers and the column counts update accordingly. Save the filter as a named view so each team member opens their own scope from the same kanban URL.

Yes. Drop the SleekView shortcode on any page and the same kanban renders. Combine that with a role-based filter so logged-in clients only see tasks in their own project. The board stays drag-and-drop for editors and read-only for clients if you set the permission that way.

By default those rows land in an Uncategorized column at the end. You can hide the column, rename it, or set a filter that excludes rows where section_gid is null. The plugin sync still pulls the rows in, SleekView just chooses how to present them.

Subtasks are stored in asana_tasks with a parent_task_gid set, and by default SleekView treats them as their own cards. If you want only top-level tasks on the board, add a filter where parent_task_gid is null. To show subtasks as a count badge instead, expose the count as a computed column on the card.