Anything that writes to wp_posts, ap_qameta, ap_votes, or to user or post meta. That includes reputation, badges, accepted-answer counts, and the standard question and answer post types. The dashboard does not care which Pro add-ons are active as long as the data lands in those tables.

Yes. Reputation lives in wp_usermeta under a key like ap_reputation. A Bar card grouped by user ID and aggregated by Sum over that meta value ranks users by total reputation. The Horizontal variant fits long display names cleanly.

ap_votes stores every vote with a vote_date column. An Area card grouped by vote_date with a Count aggregation gives a clean daily trend over the date range the card defines. Filter by vote_type to split upvotes and downvotes.

Yes. ap_votes.vote_type distinguishes vote, flag, and other vote actions. A Pie card grouped by vote_type shows the mix at a glance, useful for spotting flag spikes alongside the normal vote flow.

Yes. ap_qameta includes a selected-answer flag per question row. A card filtering questions where the selected flag is set, divided by total questions in the same range, gives an accepted-answer ratio per category or per week.

Yes. AnsPress Pro can scope categories per role; SleekView Charts respects standard taxonomy queries and shows whatever categories the current user is allowed to see, so role-gated dashboards remain consistent with front-end visibility.

Cards run paginated, indexed queries against the same tables AnsPress reads for the front end. A busy Q&A site loads dashboards at admin-list speed. For very large vote logs, scope cards by date range to keep aggregations responsive.

Yes. Save a dashboard, gate it by capability or role, and moderators, managers, and growth each land on the saved view that fits their job. One SleekView install supports several personas at once.