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

# Set your language, locale, and timezone

> Control how Biqli presents language, dates, and times.

Locale controls supported language and regional presentation. Timezone controls how dates and times are displayed in account and workspace views.

Choose the timezone where you normally interpret campaign schedules and reports. Stored activity can still be processed in a standard server timezone, so exports or API timestamps may include an explicit offset.

Changing the display timezone does not move an event to a different actual moment.

## Change localization

Open account preferences, choose an available locale and timezone, and save.
Reload affected dashboard views if they were already open.

Locale can change supported translations, date formatting, and number
presentation. It does not translate user-entered names, link labels, or imported
content automatically.

## Plan scheduled work

Use the displayed timezone when configuring activation and expiration dates.
For APIs and exports, read the timestamp offset included in the value. A time
such as `15:00+00:00` and a locally displayed `16:00+01:00` can represent the
same moment.

When a team spans regions, document the canonical timezone used for launches
and reports to avoid accidental schedule changes.

## Frequently asked questions

### Does timezone change historical timestamps?

It changes their display, not when the event occurred.

### Which timezone does the API use?

Read the explicit offset in each timestamp. Convert it in the client when a
local display is required.

### Does locale translate my link names?

No. It changes supported interface and formatting behavior, not content entered
by workspace members.

### What should a global team do?

Agree on one documented campaign timezone and include explicit offsets in
technical integrations.