Setting your default timezone

Last updated: August 5, 2026

Kula uses timezones in two places: an organisation-wide Global Timezone that acts as the account default, and a timezone on each user that drives what times that person sees and — importantly — how interview availability is calculated. This article explains how to set both.

Who can do this:

  • Global Timezone (account default): Super Admin, Admin

  • A user's own timezone: the user themselves, a Recruiter can set a missing interviewer's timezone while scheduling

Where to find it:

  • Account default: Settings → General → Global Timezone

  • Per user: Settings → My Settings --> Profile settings

Set your organisation's default timezone

The Global Timezone is the account-wide default. Kula falls back to it for a user who has no timezone of their own, and it keeps dates, times, reminders, and activity logs consistent across the account.

  1. Go to Settings → General.

  2. Find Global Timezone.

  3. Select the timezone your team primarily operates from.

  4. Click Save.

image.png

Set a user's timezone

Each user has their own timezone. Kula captures it automatically from the browser when the user first signs in, so most people never need to set it by hand. You set it manually when it's wrong or missing — most often for people who haven't logged in yet.

  1. Go to Settings → My Settings → Profile Settings.

  2. Set the Timezone.

  3. Click "Save"

image.png

A user's own timezone always takes priority over the account Global Timezone.

How Kula decides which timezone to use

When Kula needs a timezone for a person, it works down this order:

Order

Timezone used

1

The user's own timezone, if set

2

The account Global Timezone, as a fallback

3

If neither is available, times may show in UTC or not calculate at all

Good to know

  • Scheduling needs a user-level timezone. Kula enforces interviewer working hours, which requires each interviewer to have a timezone. If a selected interviewer has none, candidates see no available slots and the self-schedule link will not send until it's set.

  • Recruiters can fix a missing timezone in the moment. When you schedule with an interviewer who has no timezone, Kula alerts you and lets you set it right there, without leaving the scheduling flow.

  • Provisioned and SSO users often start with no timezone. People added through SSO, Google, Okta, or Rippling provisioning may have no timezone until their first login, which is the most common cause of "no slots" during scheduling. Set it manually at Settings → Admin → Users if scheduling is blocked before they've signed in.

Need help? If you have questions or need assistance with setup, reach out to us at support@kula.ai or use the in-app chat.