Staff can record named-booking visibility separately from team listings
This candidate adds two independent choices for venue admins with staff-edit access: whether a team member appears on the public team page, and whether clients may choose them **by name** when a service allows picking a person.
This candidate adds two independent choices for venue admins with staff-edit access: whether a team member appears on the public team page, and whether clients may choose them **by name** when a service allows picking a person. Turning named selection off does not remove the person from staff assignment or from any-available capacity. The candidate's public service lists and booking picker now distinguish these choices. New single-appointment availability, quote and submission paths enforce the choice too; Any keeps the available capacity without exposing a hidden name. App picker/recovery, grouped visits and complete Web/widget verification remain unfinished, so this is not yet an operationally complete feature. This is not a release announcement. The new column requires migration 97 and regenerated database types before rollout, followed by the booking and app companions. No hosted settings or client communications were changed. Staff identity edits and appointment policy settings are unchanged. The dedicated admin API for these two flags does not send email, SMS, or push.
Combined visits: any professional or a named one
When a client books several services as one visit on the Web or embedded booking page, they now choose between any available professional and a person the venue offers by name for every selected service. Any keeps every assigned professional available, including people the venue does not list for named booking, and the venue assigns the professional for the whole visit. Named choice only shows peo