Skip to content

Localization

Facet shows datetimes and interface text per account. Every account sets its own timezone and language on the in-app Settings page. The instance default fills the gap for accounts that follow the server. You set that default in the config file or on the platform settings page.

Set localization when:

  • You set the default timezone or language for the whole install.
  • You answer why two accounts see different times for one document.
  • You point users to their own preferences.
  • The allowed languages are en and fr.
  • The default timezone must be a loadable IANA name, for example Europe/Paris.
  • Both keys are hot: a runtime pin applies without a restart, while a config file change needs one.
localization:
default_timezone: UTC
default_language: en

The section is optional. The defaults are UTC and en. The load validates both: a timezone the runtime cannot load, or a language outside the allowlist, fails the boot.

Open Configure → Platform → Settings and set localization.default_timezone or localization.default_language. The save reaches every running process, so no restart is needed. Clear the pin to follow the file again.

The same save works through the API. The body nests one object level per path segment:

Terminal window
curl -k -X PATCH -H "Authorization: Bearer $FACET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"localization": {"default_timezone": "Europe/Paris"}}' \
"https://facet.localhost:3443/Api/core/SystemSettings/settings"

Each account key resolves in this order:

  1. The account’s own row, set on the in-app Settings page.
  2. The server default: the settings pin, then the config file, then the built-in default.
  3. The static default: UTC for the timezone, en for the language.

The mapping is core.timezone → localization.default_timezone, and core.language → localization.default_language. An account row always wins. A cleared account row follows the server.

Users open the in-app Settings page:

  • Timezone offers Auto (system timezone), which follows the browser, and Server default, which clears the account row and follows your instance default.

  • Language offers en and fr, with the same Server default option.

    Saves are instant, one field at a time. See Settings, sessions, and API keys for the user’s view.

  • Datetimes render in the account’s display timezone, across tables, audit views, datetime pickers, and CSV exports.
  • date and dateperiod values are calendar dates. They render as written and never pass through a timezone conversion.
  • The interface language cookie mirrors the account language, so the choice holds across reloads and signs-in.

Set the instance defaults for an office in Paris, and check the effective values:

localization:
default_timezone: Europe/Paris
default_language: en

Or pin the same values at runtime without a restart:

Terminal window
curl -k -X PATCH -H "Authorization: Bearer $FACET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"localization": {"default_timezone": "Europe/Paris", "default_language": "fr"}}' \
"https://facet.localhost:3443/Api/core/SystemSettings/settings"

Accounts that picked their own values keep them. Accounts on Server default switch at once.

The boot fails and names localization.default_timezone.

The value is not a loadable IANA name. Use a name the runtime can load, for example Europe/Paris.

A save answers 422 on the language.

The value is outside the allowlist. Use en or fr.

A user sees times in the wrong zone.

The account row wins over the server default. The user picks the right zone on the Settings page, or selects Server default to follow you. Auto follows the browser, not the server.

A pin change did not reach one user.

That user holds an account row for the key. The server default only fills an empty row.