Multi-country settings
The fixed Dashboard source defines Multi-country settings as the Enterprise option multi_country, routed through /all-settings?category=multi_country. It is eligible only when the project has Enterprise access and the multicountry configuration flag is enabled.
On mount, the manager requests the project's country list. Selecting an enabled country requests configuration records that the API marks as replaceable by country. The returned countries, field labels, categories, types, defaults, and values are runtime-dependent and are not established by the route alone.
The fixed client sends a country-configuration update when a text, select, or password control changes. There is no page-level draft or Save step. A production value must not be changed merely to inspect or validate the interface.
Source-defined override contract
The API accepts only configuration records marked as replaceable by country. An update must identify an existing country and eligible configuration; its value is nullable and otherwise limited to 1–2,000 characters. If no country override exists, the update path creates one. Extension hooks can alter or react to the result.
Protected configurations are returned with the placeholder PROTECT. For non-administrators, reads are limited to public, non-hidden configurations. These safeguards do not make authenticated reads or writes safe for documentation testing.
Historical fixture boundary
The retained historical screenshot and predecessor material showed a United States example with decimal, separator, distance, currency-symbol, and Stripe currency labels. That inventory is fixture evidence only. The fixed source does not prove those exact fields, that country, a Stripe setup, or their values are present in any current deployment.
Evidence and capture boundary
Safe evidence is limited to an approved synthetic country-list view with no country selected and no configuration values. Formatting, payment configuration, credentials, customer information, provider responses, and live country records remain excluded.
The fixed source establishes eligibility, request shape, override validation, protected-value handling, and immediate-write behavior. Deployed availability, returned schemas, persistence, and downstream formatting or payment effects require separate immutable receipts.
Related guides: Enterprise settings · Countries and cities