On July 6, 2026, key rotation gained its 24-hour grace window, specifically so refreshing a key could never blank a live website during the swap.
Every website's access key, scope, and switches, with misconfigurations obvious at a glance.
This guide explains the Sites screen in the Curated Sync control panel. Written for admins. Four minutes to read.
CURRENT AS OF JULY 16, 2026All eight websites, each with its own key and its own slice of the catalog.
Each of your websites is registered here with an access key, like a library card. The key maps the site to its market and warehouse, plus any narrowing rules. The screen shows each site's resolved scope: exactly which slice of the catalog that site's key returns.
Showing the resolved scope means a misconfigured site is obvious at a glance, not discovered by a customer.
Eight sites, eight keys, and a plain readout of what each one can see.
A new site gets a key shown exactly once. Copy it then; it is never displayed again.
Rotation issues a fresh key while the old one keeps working for 24 hours. A site never goes dark mid-swap.
Map the site to an office or explicit warehouses, narrow by category, or flip the public-only switch.
On July 6, 2026, key rotation gained its 24-hour grace window, specifically so refreshing a key could never blank a live website during the swap.
Key changes are built to be boring: no outages, no surprises, a full day of overlap.
A site cannot leak another market's inventory, because it never receives it.
The library filters by the key before serving anything. Raleigh's key returns Raleigh inventory, full stop. There is nothing for the website to filter out on its end, and nothing to get wrong.
Per-site visibility rules add a finer brush on top, and they are off by default. See the Visibility screen guide for how those preview before they activate.
Scope is enforced at the source. The wrong products never leave the building.
Rotate it. The new key is shown once, and the old one keeps working for 24 hours while you update the website.
Scope maps a site to its office and warehouse. Products stocked in both warehouses appear on both sites, because that reflects reality.
When on, the site only receives products marked public. It is one more filter applied before data leaves the library.
The Sites screen is where trust is configured: who reads the library, and exactly how much of it.