Release 1.15.6 · LAP hosted sites now tie to a verified domain—and your old manual site ids go away

Hosted LAP pages were previously registered with a free‑typed “site segment.” That made it easy for the segment and the real customer hostname to drift apart, and it complicated routing and support. This release makes each hosted site one‑to‑one with a verified LAP domain for your organization. When you register a site, you pick the domain; the storage folder name is derived from that hostname so uploads, routing, and what you see in the dashboard stay aligned.

What you need to do

After deploy, open LAP → Sites and register each site again using the domain picker. Earlier registry rows are cleared by the database migration so segments cannot silently disagree with DNS. Re-upload hosted files for each site if you rely on the hosted-pages bucket; paths are keyed by the new segment rules tied to the domain. If you use custom domains for LAP, keep using your existing DNS and verification flow. If domain verification fails after this update, read the status message on the domain: we no longer mark a domain “verified” when the load balancer could not finish the LAP static routing step, so you fix routing before visitors assume SSL is fully ready. What improves for you

Clearer create flow: choose a verified LAP domain, see a read‑only preview of the storage segment, optional display name, then go straight to uploads. Domains list on the LAP sites screen works for roles that can manage LAP sites without needing the broad “read every org domain” permission, using the same safe “reference lister” pattern used elsewhere. Safer GCP behavior: if the shared LAP path matcher is missing the /lap-api rules our automation clones from, the backend fails fast with an explicit error instead of publishing host rules without API routing.