---
title: Configuring time zones
related:
  - https://docs.kentico.com/13/multilingual-websites/changing-the-date-and-time-format.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

The **Time zones** application allows you to configure time zones that will be available in the system. You can set time zones for the following:

- particular **[users](#setting-time-zones-for-users)**
- particular **sites**
- physical location of the **server**

This can be useful if your website has international staff, and you want the date and time displayed in the administration interface to be correct for users across the world.

To use time zones, enable the feature in the settings:

1. Open the **Settings** application.
2. Navigate to **Settings** -> **System**.
3. In the **Time Zones** section, select the **Enable time zones** checkbox.

   ![Time zones in the Settings application](https://docs.kentico.com/docsassets/13/configuring-time-zones/time_zones_in_the_Settings_application.png "Time zones in the Settings application")
4. Click **Save**.

Time zones are currently supported in various applications throughout the Xperience administration interface.

> **Tip:** **Changing server time zones in Azure-hosted applications**
>
> Changing the server time zone using this approach is not possible in Azure-hosted applications. Furthermore, due to the nature of cloud-based services, the server hosting your application changes frequently. These changes are also reflected in event time-stamps and other places where server time is displayed or used, which may be undesirable.
>
> If you wish to persistently configure the time zone for Azure-hosted applications, follow the instructions outlined in [Changing the server time zone on Azure](https://blogs.msdn.microsoft.com/tomholl/2015/04/06/changing-the-server-time-zone-on-azure-web-apps/).

## Usage example

**Day and time in the Pages application**

[User time zone](#setting-time-zones-for-users)

- User Andy sets the _Publish from_ value of a page to _3/14/2016 3:14:15 PM_. His user time zone is set to _UTC+00:00 (London)_.

![Day and time value relative to London time zone](https://docs.kentico.com/docsassets/13/configuring-time-zones/pages_publish_from_UTC_plus_00-00.png "Day and time value relative to London time zone")

- User Claire selects the page and sees that the _Publish from_ value is _3/14/2016 11:14:15 AM_ because her user time zone is set to _UTC-05:00 (New York)_.

![Day and time value relative to New York time zone](https://docs.kentico.com/docsassets/13/configuring-time-zones/pages_publish_from_UTC-05-00.png "Day and time value relative to New York time zone")

Site time zone

- If a user has no time zone specified, the day and time values are relative to the _Site time zone_. In this example, the site time zone is set to _UTC+01:00 (Paris)_.

![Day and time value relative to Paris time zone](https://docs.kentico.com/docsassets/13/configuring-time-zones/pages_publish_from_UTC_plus_01-00.png "Day and time value relative to Paris time zone")

Server time zone

- If neither _user time zone_ nor _Site time zone_ are specified, the _Server time zone_ is used.

## Setting time zones for users

Each user can have their own time zone settings:

1. Open the **Users** application.
2. Edit () a user.
3. On the **Settings** tab, select a time zone from the **Time zone** drop-down list.
4. Click **Save**.

Where applicable, these time zone settings are used instead of the _Site time zone_.