No. SleekView writes only a local hide flag or retry trigger to the gce_feed_cache row, the Google source event stays exactly as the organiser left it. This keeps the WordPress display fully under the calendar manager's control without ever pushing back to Google through the API.

Yes. SleekView reads the status field from each gce_feed_cache row and renders one column per distinct value. Confirmed, Tentative, and Cancelled show as the three Google-side columns, with the local Sync error column added when the last sync meta on the feed reports a failure.

Yes. Dragging a Sync error card back to Confirmed triggers the same retry path the feed settings sync now button uses, but scoped to the single event ID. SleekView writes the retry trigger on the cache row and the feed scheduler picks it up on the next run within the configured interval.

Yes. The board can aggregate gce_feed_cache rows across every gce_feed post on the install, or be filtered to a single feed by feed ID for a per-calendar view. The grouping field stays the Google status, only the filter changes per saved view for each calendar manager.

Yes. SleekView reads any custom field you added to gce_feed_cache through a snippet and lets you choose it for the card front. The value matches what the cache row holds because SleekView reads the same row, not a copy stored somewhere else inside the WordPress database.

Yes. Saved kanban views are scoped per role and per capability, so calendar managers can see Confirmed and Tentative only, developers can see Sync error, and admins see every column. The underlying gce_feed_cache data does not change, only what each role reads on the board.

Yes. SleekView reads the live gce_feed_cache rows on every load, so the next time a scheduled sync runs and updates the cache the board reflects the new statuses on the next refresh. There is no separate index to rebuild because the board reads the same rows the front-end feed reads.

No. SleekView paginates inside each column and loads card detail on demand, so a feed with several thousand cached events renders the column counts immediately and streams card content as you scroll. Filters and saved views reduce the working set before render.