Yes. SleekView reads the Pro recurrence meta and shows the recurrence pattern on the card front by default. A recurring series appears as a single card with the next occurrence and the recurrence indicator, or you can expand it to one card per occurrence if your workflow tracks them separately.

Yes. Dropping a card into the Published column writes publish to post_status on the underlying tribe_events post, which fires the same transition_post_status hooks the default admin does. The public Events Calendar Pro reads the new value and the event appears with the Pro recurrence applied.

Yes. SleekView discovers the Pro additional fields you have defined and lets you choose any of them for the card front. Editorial flags, sponsor names, approval owners, and any custom field you read every day can sit on the card without opening the record.

Yes. SleekView reads the distinct values present in post_status and renders one kanban column per value. If you have registered a custom post status like Cancelled, Postponed, or Sold out through a snippet or extension, those appear next to the built-in WordPress statuses without extra setup.

Yes. Saved kanban views are scoped per role and per capability, so writers can see Draft and Pending review only, editors can see all columns, and contributors can drag only their own posts. The WordPress capability checks on edit_post still apply on every drag.

The board can show events across every calendar or be filtered to a single venue, category, or organiser from the SleekView filter bar. For a multisite editorial team you can save one board per site, with each saved view scoping reads and writes to the events in its scope.

Yes. Every drag writes a row to the SleekView activity log with the event ID, the previous status, the new status, the user who made the change, and the time. The log is filterable per event so reconciling a publishing question after the fact is a single search rather than a postmortem across screens.

Yes. SleekView only loads cards for the columns currently visible and paginates older events into a scroll-on-demand tail. The events admin and the board read the same underlying posts so neither slows down as the archive grows.