No. The Easy Appointments admin list and calendar stay where they are. SleekView Charts sits alongside as a configurable layer so reception, owners, and finance each get a chart dashboard the plugin doesn't ship today, without altering the day-to-day workflow at all.

Yes. wp_ea_meta_fields rows can be pivoted into typed columns by field key. SleekView uses each typed column as a chart's groupBy or valueColumn, so custom intake fields collected on the booking form become charts without writing any SQL or PHP.

wp_ea_connections joins onto the appointment dataset and resolves worker, service, and location IDs to readable labels. A single saved configuration drives the join, so every card on the dashboard uses the same connection mapping consistently.

Yes. A horizontal Bar grouped by worker with a counted aggregation ranks workers by appointment volume. Filter the dashboard date range and the ranking scopes automatically, so a busy month and a slow quarter use the same saved chart configuration.

Yes. A date range, worker filter, or service filter at the dashboard level cascades to each card on the board. A weekly capacity review and a quarterly trend can share one saved configuration without per-card duplication of filter selections.

Cards query the live Easy Appointments tables on render. A new booking created from the frontend form or admin appears in every card on the next reload, with no separate sync, scheduled refresh, or cache flush to wait on between updates.

Yes. Aggregations run server-side using the indexes Easy Appointments already maintains on its tables. A multi-worker install with thousands of historical appointments renders the whole chart board in well under a second on a typical Kinsta host.

Yes. Each saved board is gated by a WordPress capability, so reception, owners, and finance each open the dashboard that matches their job. The worker utilisation board and the finance revenue board stay separate by default for each user.