Time Zone Settings

Time zones help users contextualize the information that PagerDuty displays within incidents and schedules. When users are added to an account, their time zones will match the account-level time zone by default. Users can change their user-level time zone if necessary. Regardless of the account-level time zone, on-call schedules are displayed in the user’s preferred time zone.

Change the Account-Level Time Zone

The Account Owner can change the account-level time zone in the web app:

  1. Navigate to User Icon Account Settings Account Settings tab.
  2. Under Account Details, select the Default Time Zone from the dropdown.
  3. Click Save Changes.
Default Time Zone set to "PST Pacific Time"Default Time Zone set to "PST Pacific Time"

Default Time Zone set to "PST Pacific Time"

Change the User-Level Time Zone

Any user can adjust the time for their own account:

  1. Navigate to User Icon My Profile Contact Information.
  2. To the right of Time Zone, click .
Edit user-level time zoneEdit user-level time zone

Edit user-level time zone

  1. Select the desired time zone from the dropdown.
  2. Click Save.

Change the Schedule-Level Time Zone

🚧

Required User Permissions

Users with the following roles can create, edit and delete on-call schedules:

  • User
  • Admin
  • Manager base roles and team roles
    • Manager team roles can only manage schedules associated with their team.
  • Global Admin
  • Account Owner

Note: Free plans are limited to one schedule.

When you create a new schedule, it will be set to the account-level time zone by default. You may, however, adjust the schedule’s time zone to differ from the account’s time zone. Before changing a schedule with users in multiple time zones, please read the section on how Daylight Saving Time may affect your schedules.

To change a schedule's time zone:

  1. Navigate to People On-Call Schedules next to your desired schedule Edit.
  2. In the Time zone dropdown, select your preferred time zone.
  3. Click Save Changes.
Schedule Time zone set to "Pacific Time"Schedule Time zone set to "Pacific Time"

Schedule Time zone set to "Pacific Time"

Daylight Saving Time

If your account has users in different time zones, there are a few things to keep in mind with respect to how Daylight Saving Time (DST) may impact your schedules:

  • A schedule will default to the account-level time zone. You can, however, change the schedule's time zone if you do not wish for it to match the account’s time zone.
  • Users who are not in the same time zone as the schedule will still view it in their own time zone. For example, if a schedule is configured in USA EST and it is 9:00 a.m., but user Marge has set her account to USA PST, her view of the schedule will reflect 6:00 a.m.
  • In the case of DST discrepancies between users’ and schedules’ time zones (the user’s time zone observes DST but the schedule’s does not, for example, and vice versa), the above details still apply. Users in this situation should take note of the following and the potential impact to their schedules:
    • Example 1: If a schedule is set to USA EST (observing DST) at 2:00, but user Jon has his account set to UTC (not observing DST) at 7:00, when DST begins in the schedule's time zone, his view of his schedule will advance to 8:00, but his clock will remain at 7:00.
    • Example 2: If a schedule is set to UTC (not observing DST) at 7:00 and user Emily’s account is set to US EST at 2:00, when DST begins in Emily’s time zone, her clock will advance to 3:00, but her view of her schedule will remain at 2:00.

📘

Tip

When creating schedules with users in multiple time zones, we recommend taking note of the schedule’s time zone and communicating it to any users who may be affected by the observance/non-observance of DST.

Exceptions

Most times in the PagerDuty web app are displayed in the logged-in user’s time zone. There is a notable exception: if your account has Advanced Reporting, the System, Team and User reports are displayed in the account-level time zone.

Additionally, any time-related information gathered from the REST API, such as incident trigger times, are displayed in UTC.


Did this page help you?