Regional Settings

The Regional tab in Partner Settings holds partner-level localization defaults: timezone, date and time format, and console language. These are the defaults new organizations and sites inherit when they are created under the partner, so setting them once establishes a consistent baseline across the tenant.

Reach it at Settings → Partner → Regional (the tab is anchored at #regional). Changes are saved to the partner’s settings JSONB via PATCH /orgs/partners/me, where the keys are merged rather than replaced. The timezone additionally populates the first-class partners.timezone column.

---

Regional Settings

Setting	Options	Default	Notes
Timezone	Any IANA timezone, via a searchable picker (~400+ zones)	UTC	The canonical timezone default for the partner.
Date Format	MM/DD/YYYY (US), DD/MM/YYYY (International), YYYY-MM-DD (ISO)	MM/DD/YYYY	Controls how dates are rendered in the console.
Time Format	12-hour or 24-hour	12-hour	Radio toggle.
Language	English (en), Português (Brasil) (pt-BR), Español (Latinoamérica) (es-419), Français (France) (fr-FR), Français (Canada) (fr-CA), Deutsch (Deutschland) (de-DE), Italiano (Italia) (it-IT), or Türkçe (Türkiye) (tr-TR)	en	The console display language.

Note

Non-English catalogs are machine drafts pending native review. The console falls back to English for any string not yet translated.

Note

Business hours are not on this tab. The calendars that SLA deadlines are counted on now live at Settings → Ticketing → Priorities & SLAs → Business hours. See Ticketing → Business hours.

Note

Currency is not on this tab. Your billing currency lives at Settings → Billing (the setup wizard also asks for it during the Regional step). New organizations are stamped with the partner currency when they are created and are not rewritten if you change it later. See Invoices → Where the currency comes from.

---

How it cascades

The Regional tab sets partner defaults. New organizations and sites created under the partner inherit these values as their starting point. Existing records are not retroactively rewritten when the partner defaults change — update those individually if needed. Sites also carry their own timezone field (defaulting to UTC) that can override the inherited value per location.

---

Related

• Partner Management — the partner record, self-registration, and the settings JSONB these values live in.
• Organizations & Sites — the hierarchy that inherits these regional defaults, including per-site timezone.