Public team and service descriptions
Connected Sites team sections and newly generated service-page facts now use the same active, publicly listed provider authority as BookingBible's public provider catalog. A service assignment alone does not authorize publishing a person's identity. Private or suspended memberships and collaboration public-listing withdrawals are respected; unreadable listing or identity information is withheld.
Connected Sites team sections and newly generated service-page facts now use the same active, publicly listed provider authority as BookingBible's public provider catalog. A service assignment alone does not authorize publishing a person's identity. Private or suspended memberships and collaboration public-listing withdrawals are respected; unreadable listing or identity information is withheld. Public service facts use the venue's display-name override, then the professional's chosen display name, instead of substituting a legal name or an invented “Instructor” label. The existing portable-identity control still governs venue bio, photo and title overrides. This applies to class, appointment-only, hybrid and neutral businesses. It does not grant staff access, change booking eligibility or modify the collaboration/free-venue model. The named-provider booking picker remains a separate policy surface. Dynamic team data and future generation inputs are updated; already authored or published page text is not automatically rewritten or erased. Existing brand-site team restrictions, templates, site navigation and publish controls are unchanged. No notifications are sent. Business app authoring, mixed-venue Consumer and Branded app flows keep their existing APIs; this Sites read-side companion adds no native screen or custom-terminology support. Local regression verification is required before integration; this note is not deployment evidence.
Service image authoring and recovery
Web service editing and the Business-app API companion now share one venue-scoped image writer. Authorized admins with bookings.manage can upload JPG, PNG or WebP (up to5 MiB, at least1200 by675 pixels), then save a16:9 catalog image. Existing service-catalog franchise locks also apply. The writer validates owned original paths and bytes, creates immutable1600/800/400 WebP versions, and compares t