This article explains how timezones are set and modified when you create or edit sessions, OKRs, and key results.

For example, if you set the session to end date on the first day of each month, you should make sure that on the last day of the month, the session does not end, because of timezone differences.

Session timezone

  • Create a session
    When you create a new session, it automatically inherits your timezone.

    EXAMPLE: If your timezone is UTC+1, then the session’s time frame will be set in this timezone. This means that the account’s current time zone for this specific session is also UTC+1. Thus, the session’s deadline will be at 23:59:59 UTC+1 on the specified day.

  • Edit a session
    When you edit an existing session, it automatically inherits your time zone, regardless of the timezone of the user who created the session.

    EXAMPLE: If you make any changes to the session and your timezone is UTC+5:30, the timezone of the session automatically changes to UTC+5:30. Thus, the session’s deadline will be changed to 23:59:59 UTC+5:30 on the specified day.

OKRs timezone

If you do not specify anything other, when creating an OKR, it automatically inherits the session’s time frame and timezone.

If you edit a session and if your timezone is different than the one of the user who created it, both the session’s and the OKRs’ timezones change to your timezone.

Key results timezone

When you create or edit the key results' hard deadline, it is automatically set to your timezone.

For more information, see Key result deadlines.

Account timezone

The session timezone and time frame are not related to the account timezone settings. The account timezone applies to the reports and the reminders that are being sent.

For more information, see Configure the Aggregated OKR report.

Did this answer your question?