No. The Team Booking admin list and calendar stay where they are. SleekView Charts sits alongside as a configurable layer so studio managers, reception, and finance each get the chart dashboards the plugin doesn't ship today, without changing day-to-day workflow.

Yes. Reservation start, end, price, customer email, and any custom field from wp_postmeta can be pivoted into a typed column. SleekView uses that column as a chart's groupBy or valueColumn, so custom-segment Pies and custom-numeric Bars are straightforward to build.

wp_term_relationships joins onto the dataset, so a Donut grouped by tb_service term shows the booking distribution across services without any custom code. The taxonomy filter at the dashboard level cascades through every card on the saved board.

Yes. A horizontal Bar grouped by the staff Google Calendar account ID with a Sum aggregation on duration_minutes ranks staff by booked hours. Filter by service or by date range to scope the ranking to a specific period or focus area.

Yes. A date range, service term, or staff filter at the dashboard level cascades to each card. A weekly capacity review and a quarterly trend can share the same saved configuration without duplicating filter selections card by card.

Cards query wp_posts and wp_postmeta live on render. A new reservation created through the booking form or admin appears in every card on the next reload, with no separate sync, scheduled refresh, or cache flush to wait on.

Yes. Aggregations run server-side using the indexes WordPress already maintains on post type, post date, taxonomy, and meta keys. A multi-staff install with years of reservation history renders the whole board in well under a second.

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