Community Events writes a recognisable origin signal on submitted rows, typically a meta key plus the submitter as post_author. The dataset filters on that signal so editorial events created directly in wp-admin do not inflate the queue, the pace card, or the submitter ranking.

Yes. While the Number card shows the count, a separate SleekView table view over the same dataset can sort pending rows by post_date_gmt ascending so moderators see the oldest unhandled submission first. The charts and the table share the same data.

Yes. Community Events supports both logged-in and anonymous submission flows. Anonymous rows carry the configured default author, so the submitter bar surfaces the configured account rather than blank cells. The pipeline view still works on the daily pace card the same way.

Yes. The Tribe event category taxonomy is exposed as a column, so a pie or bar card grouped on that taxonomy returns the count of submissions per category. Moderators can see whether the community is contributing across the full programme or only one niche.

Yes. If a submitter account is later removed, the post_author column still holds the historical user ID. The join falls back to a placeholder label so the bar card does not break, while the underlying row remains queryable in the table view alongside.

Yes. Every card has a filter scope that targets post_date_gmt. A daily pace card filtered to the campaign window returns only that period's submissions, which makes it straightforward to attribute community contributions to a specific marketing push.

Yes. SleekView respects WordPress capabilities. Moderator roles see the dashboards configured for them, and edit operations performed in the table view honour the same capability checks Community Events enforces on the pending screen.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when reviewing the actual submissions behind a sudden spike on the pace card or behind a top-submitter on the bar card.