Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 0 additions & 27 deletions guides/developer/timezones.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,16 +15,8 @@ This guide is in two parts:
**tl;dr:** store timestamps as timezone-aware types, use `DATE` for calendar values, and set your [project timezone](#configure-your-project-timezone) to the zone you report in.
</Info>

# Timezone Setup

<Info>
**tl;dr:** store timestamps as timezone-aware types, use `DATE` for calendar values, and set your [project timezone](#configure-your-project-timezone) to the zone you report in.
</Info>

## Timezone conversion

Lightdash converts the timezones of your data from their **source timezone** to a **report timezone**:

Lightdash converts the timezones of your data from their **source timezone** to a **report timezone**:

- [**Source timezone**](#configure-your-connection) is the timezone of the raw data. It is defined in your warehouse, data types, modelling, and connection settings.
Expand Down Expand Up @@ -94,19 +86,6 @@ In **Project settings** → **Timezone**, pick the zone you want reports to use.
/>
</Frame>

<Frame>
<img
alt="Project query timezone field in Project Settings"
className="block dark:hidden"
src="/images/guides/developer/timezones/project-query-timezone-setting-light.png"
/>
<img
alt="Project query timezone field in Project Settings"
className="hidden dark:block"
src="/images/guides/developer/timezones/project-query-timezone-setting-dark.png"
/>
</Frame>

By default the project timezone is UTC, which means all reports in Lightdash default to showing results in UTC. The project timezone can be [customised per chart or user](#report-timezone-resolution).

## Opt a column out of timezone conversion
Expand Down Expand Up @@ -215,12 +194,6 @@ If it's not the zone you expect, change it with the [timezone picker](#choosing-

A chart's own timezone setting decides what zone it uses, unless an embed overrides it. The zone it ends up using is its **resolved timezone**, the term used throughout this guide. From highest priority:

1. **A direct embed's** `timezone `**URL parameter** (on iframe or shareable-URL embeds only, see [Embedded dashboards](#embedded-dashboards)). This outranks everything.
2. Otherwise, the chart's timezone setting applies:
- **Project timezone** (the default): the project's timezone, for every viewer.
- **User timezone**: the viewer's profile timezone, or the project timezone if they haven't set one.
- **A specific timezone**: that exact zone, the same for everyone.

1. **A direct embed's** `timezone `**URL parameter** (on iframe or shareable-URL embeds only, see [Embedded dashboards](#embedded-dashboards)). This outranks everything.
2. Otherwise, the chart's timezone setting applies:
- **Project timezone** (the default): the project's timezone, for every viewer.
Expand Down
Loading