Any plugin that creates draft or pending posts. The aggregation reads wp_posts and wp_postmeta directly without coupling to a specific plugin's API. User Submitted Posts, WPUF, Frontend Publishing Pro, and any custom form-to-post setup all work.

By default no. The cards scope to draft and pending statuses, which is the moderation queue. To track approved volume over time, add an approved filter and a separate Area card with post_status=publish for trend reads.

Yes. Save the dashboard with a category filter per editor. Each opens their own cohort's view without changing the underlying data. WordPress capability gating limits dashboard visibility per role too.

No. SleekView Charts is read-only over stored posts. Status changes still route through wp_update_post via SleekView's table view or the regular admin, and any plugin reading post status keeps working.

Yes. ACF, Meta Box, and plain postmeta fields all become group-by options. Author reputation, source IP, or topic field can each drive a chart card.

Filters scope the cards before aggregation, so a known-bad-pattern filter (disposable email domain, suspicious IP) reduces what each card counts. Combine with a daily-volume Area card to read whether the wave is escalating.

If the submission plugin stores the reviewer on the post (assignee meta), yes. Group a Bar card by reviewer to read who handles what share of the queue. Useful for editorial team management.

By default yes, because they live in the same draft pool. Filter by author role or by a submission-plugin meta key to exclude editor-authored drafts from the submission dashboard.