> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threataware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings → Timezone

> Tenant default timezone + region, plus per-user overrides

## The page

At `/settings/timezone`:

<img src="https://mintcdn.com/threatawareltd/IwzdezxNqgZB-5I4/images/core/settings-timezone.png?fit=max&auto=format&n=IwzdezxNqgZB-5I4&q=85&s=d3b019add11ca5667c357c65351efb56" alt="Timezone page with Client Locale (Timezone, Region) and User Locale (Use Client Settings) sections" width="1440" height="900" data-path="images/core/settings-timezone.png" />

Two sections:

### Client Locale (tenant default)

*"The timezone and region settings for the client. These settings will be used for all users on the client."*

* **Timezone** — IANA timezone (e.g. `Europe/London`, `America/New_York`)
* **Region** — culture / locale (e.g. `en-GB`, `en-US`)

These defaults apply to every user unless they override.

### User Locale (per-user override)

*"The timezone and region settings for your user. These settings will override the client settings."*

* **Timezone** — defaults to `Use Client Settings`; set to override
* **Region** — defaults to `Use Client Settings`; set to override

## Why these settings matter

Timezone affects:

* **Date / time display** everywhere in the product (top-right clock, audit log timestamps, last-seen times)
* **Scheduled Reports** delivery time
* **Action automations** that include timestamps in payloads
* **API responses** — timestamps in API output use the requesting user's tz (default) or UTC if specified

Region affects:

* **Date format** (e.g. `19/05/2026` vs `05/19/2026`)
* **Number formatting** (thousands separators, decimal markers)
* **Currency rendering** in Studio apps

## Setting tenant defaults

Super Admin only:

1. Choose your organisation's primary timezone — usually the location of your operational team, not necessarily your HQ
2. Choose the region — `en-GB` for UK English, `en-US` for US English, etc.
3. Save

Every user without a personal override now follows these.

## Per-user overrides

Each user can override their own locale from this same page (under User Locale). Useful for:

* Distributed teams across multiple timezones
* Field engineers reporting from different regions
* Analysts who prefer specific date / number formats

## Best practices

<AccordionGroup>
  <Accordion title="Pick the operational team's timezone, not HQ's">
    A US-headquartered company with a London SOC should probably set the tenant default to Europe/London, because the SOC reads the timestamps daily and HQ doesn't.
  </Accordion>

  <Accordion title="Communicate scheduled-report times in the tenant TZ">
    "Weekly report Mondays at 8am" is unambiguous when everyone reads from the tenant TZ. Avoid "08:00 UTC" in human-facing copy unless you know your audience is distributed.
  </Accordion>

  <Accordion title="Audit log timestamps follow viewer TZ">
    When pulling audit-log evidence for a third party, mention which TZ the timestamps are in (or set your User Locale to UTC during the export).
  </Accordion>
</AccordionGroup>