Scheduler — the appointment book — It configures itself

A scheduler needs to know more than a calendar does: not just when, but who is delivering the appointment, what it is, and who it is for. It works those out for itself, in this order. 1. What you chose. Anything set on the view wins. 2. Your booking page. If the table already takes public bookings, that page has answered these exact questions — which link is the staff member, which is the client — so the scheduler inherits them rather than asking twice. Re-point the booking page and the scheduler follows; nothing is copied onto the view to go stale. 3. An unambiguous single candidate. One link called Staff, one called Service, one Select called Status: taken. Two that could each be the staff member: neither, because guessing wrong books somebody with a haircut instead of a stylist. Every role is optional. No status field means no status buttons; no staff link means no per-person columns and the day is shown instead, with a picker to fix it.