Public venue team listings can include active service providers and instructors, including a delivery capability on another primary role. A generic staff account is not automatically a public professional. The venue's public-listing setting and professional collaboration withdrawals remain authoritative.

The venue instructors API and appointment venue-team loader share this listing policy and tenant-specific display overrides. A requested brand must belong to the requested venue; an unknown brand or failed assignment read cannot silently widen the roster. The instructors response is private/no-store so a shared CDN cache cannot extend a withdrawn listing's visibility. Already-loaded client screens and published/generated content are not recalled by this change.

Unreadable collaboration consent omits the owned public listing. The old authenticated-directory withdrawal wrapper retains its legacy behavior; this is not a claim that every directory or Sites projection has been hardened. Sites integration remains separate.

Public team-page visibility is distinct from operational service assignment and booking eligibility. This change deliberately does not alter the service-specific booking picker, availability, assigned booking history or professional collaboration architecture. A separate owner decision is pending on whether hiding a team profile should also hide selection by name when booking.

Root verification uses actual loader/API functions with controlled database, switch and rate-limit boundaries. It does not establish hosted data changes, device behavior or production delivery. Native custom terminology and full Business resource/setup authoring remain separate unfinished companions.