Setting your organization's timezone is an important step to ensure your automated tasks run exactly when you expect them to.

> **Important Note on Time Display:** The organization timezone **only** dictates when automated background tasks (like scheduled scanning) are executed. The times you actually see displayed inside the Catcher24 dashboard (such as report generation times or scan logs) will **always be shown in your current device's local timezone**. The organization timezone does not change your dashboard display.

## Step-by-Step Instructions

1. **Access Organization Settings** From your Catcher24 dashboard, navigate to the left-hand menu, click on **Settings**.

   ![](https://support.catcher24.net/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBSQT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--1d6efe716e879e43dcff8ad363d61a8b5161bccc/OrganizationSettings.png)  

2. **Select Your Organization Timezone** Locate the Timezone dropdown menu. Select the primary timezone where your organization operates or where you want your system's "clock" to be anchored. 

   ![](https://support.catcher24.net/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBSUT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--86ddc158d42ed0b0b39140c5c6362dae62c94509/Screenshot%202026-04-21%20121115.png)

3. **Step 4: Save Your Changes** Scroll to the bottom of the page and click **Save**.

## How This Affects Scheduled Scanning

When you set up a recurring scheduled scan, the scan will execute based on the **Organization Timezone** you just selected.

Choosing a location-based timezone (like `Europe/Amsterdam`) instead of a fixed UTC offset is highly recommended, as it dictates how your automated tasks handle time changes throughout the year.

* **The DST Advantage:** By selecting `Europe/Amsterdam`, Catcher24 automatically adjusts for Daylight Saving Time. If you schedule a daily scan for `02:00`, it will consistently run at `02:00` local Amsterdam time year-round - seamlessly shifting between Central European Time (CET) in the winter and Central European Summer Time (CEST) in the spring. If you had selected a fixed offset like `UTC+1` instead, your scans would run an hour late during the summer months.

* **The Display Difference:** Remember that your dashboard converts times to your local device clock. If your Organization Timezone is `Europe/Amsterdam` and the scan runs at `02:00`, a team member logging in from London will see the scan recorded at `01:00` on their dashboard, because their local device is one hour behind Amsterdam.

## Troubleshooting & FAQs

**I scheduled a scan for 09:00, but my dashboard says it ran at a different time. Did it fail?** Most likely, no! It ran at `09:00` according to your *Organization's* timezone, but your dashboard is displaying the time according to your *computer's* current local timezone. Verify your device's clock settings if the time difference seems incorrect.

**What happens to scans scheduled between 02:00 and 03:00 during the spring DST clock change?** When clocks spring forward and skip that hour entirely, Catcher24 will automatically execute any scans scheduled during that skipped window immediately at the `03:00` mark to ensure no tasks are missed.

**Can individual users set their own timezone for scheduled scans?** No. To prevent conflicting schedules and ensure consistent automation, all automated scans run strictly on the single, global Organization Timezone set by the Administrator.