# Create a timezone picker for your end users

**URL:** <https://community.omni.co/t/create-a-timezone-picker-for-your-end-users/456>\
**Category:** Modeling\
**Tags:** modeling\
**Created:** [April 22, 2026, 1:20pm UTC](https://community.omni.co/t/create-a-timezone-picker-for-your-end-users/456 "2026-04-22T13:20:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jiro](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.omni.co/jiro/32/268_2.png) [@Jiro](https://community.omni.co/u/Jiro)\
**Post date:** [April 22, 2026, 1:20pm UTC](https://community.omni.co/t/create-a-timezone-picker-for-your-end-users/456/1 "2026-04-22T13:20:35Z")

</div>

**The Problem**

**UPDATE** - once enabled in the org Settings panel, you can show users a timezone override dropdown in dashboards ([demo here](https://docs.omni.co/demos/2026/20260501#time-zone-overrides) – expected to be available week of May 4th)

Some use cases require flexibile timezone presentation to really get the context of the data point. If you have just a few you can solve that with static timezone converted timestamp fields for each (i.e created\_at\_utc, created\_at\_bst, created\_at\_est) but that can get out of hand as the list grows.

**The Workaround: A Templated Filter + Model-Level Conversion**

Instead of relying on static conversions, you can build a timezone picker directly into your dashboard using a templated filter and a timezone conversion function in your model SQL.

**Step 1: Define a timezone picker filter in your model**

```auto
filters:
  timezone_picker:
    type: string
    suggestion_list:
      - value: America/New_York
      - value: America/Chicago
      - value: America/Los_Angeles
      - value: Europe/London
      - value: Europe/Paris
      - value: Asia/Tokyo
    default_filter:
      is: America/New_York
    filter_single_select_only: true

```

**Step 2: Apply the conversion in each timestamp dimension**

Use a `CASE WHEN` to detect whether the filter is active before applying the conversion, so the field degrades gracefully when no timezone is selected (update the field reference and specific timezone conversion syntax for your database dialect if you don’t use Snowflake):

```auto
dimensions:
  created_at_tz:
    label: Created At (User Timezone)
    type: timestamp
    convert_tz: false
    sql: |-
      CASE WHEN {{your_view.timezone_picker.is_filtered}}
      THEN CONVERT_TIMEZONE('UTC', {{ filters.your_view.timezone_picker.value }}, ${your_view.created_at})
      ELSE ${your_view.created_at} END

```

Default Timestamp in UTC

 ![Screenshot 2026-04-22 at 1.59.08 PM](https://canada1.discourse-cdn.com/flex004/uploads/omni/original/1X/86e5eaa2227b84d4b4ce51c75c12e3270d43830f.png)

User notices the order is from Minnesota and selects the appropriate timezone to see the order time locally

 ![Screenshot 2026-04-22 at 1.59.18 PM](https://canada1.discourse-cdn.com/flex004/uploads/omni/original/1X/82522caa244bdff557be2c5e1dc2856fa98c85aa.png)

**Key things to know**

- The `timezone_picker` filter can be shared across multiple dimensions and views, as long as it’s included in the topic — you don’t need a separate filter per timestamp.
- You will need to update the SQL for each timestamp dimension you want to convert.
- though most modern data warehouses can optimize queries to make this CASE STATEMENT not be too costly, you should test for query performance if operating on excessively large tables.

**What’s next**

This workaround gives end users a self-service toggle to switch timezones without requiring a new session. A native event-based mechanism to update the user timezone without regenerating a session has been noted as a product request (eta early May 2026).

---

<div class="post-metadata">

**Author:** ![ShivaPrasad](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.omni.co/shivaprasad/32/651_2.png) [@ShivaPrasad](https://community.omni.co/u/ShivaPrasad)\
**Post date:** [May 2, 2026, 2:34am UTC](https://community.omni.co/t/create-a-timezone-picker-for-your-end-users/456/2 "2026-05-02T02:34:44Z")

</div>

Thanks for sharing this Jiro!

For situations where there is only 1 predefined timezone for a database, I know that omni allows “User specific timezones” on the connection settings page. And omni allows setting the preferred query timezone at a User profile level for Org users, but not Embed users. Are there any plans to support this for Embed users too?

 ![image](https://canada1.discourse-cdn.com/flex004/uploads/omni/original/1X/05ef8afe2e7821c898146175348dbc8a08505858.png)

Org user settings page:

 ![image](https://canada1.discourse-cdn.com/flex004/uploads/omni/original/1X/3f45651987fcba70dc4d89964bab3b89b9248150.png)

Embed user settings page:  
(no options in the user tab, and no api way to set the query timezone)

 ![image](https://canada1.discourse-cdn.com/flex004/uploads/omni/original/1X/6d0ab09298e508e56a3abba0a537356cd3296cc0.png)

While we wait for something like this, your solution is a good workaround, with the added bonus of easily being able to switch timezones at the dashboard level.

---

<div class="post-metadata">

**Author:** ![Jiro](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.omni.co/jiro/32/268_2.png) [@Jiro](https://community.omni.co/u/Jiro)\
**Post date:** [May 4, 2026, 2:22pm UTC](https://community.omni.co/t/create-a-timezone-picker-for-your-end-users/456/3 "2026-05-04T14:22:18Z")

</div>

Hi Shiva! Yes you can pass a user specific timezone for embed users in the userAttributes parameter. [Example here](https://docs.omni.co/embed/setup/url-parameters/userAttributes#examples)

That being said, we’ve had a demo just this last week of an end user timezone selection coming soon (this week perhaps) so may not be worth implementing a workaround [May 1, 2026 - Omni Docs](https://docs.omni.co/demos/2026/20260501#time-zone-overrides)

---

<div class="post-metadata">

**Author:** ![ShivaPrasad](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.omni.co/shivaprasad/32/651_2.png) [@ShivaPrasad](https://community.omni.co/u/ShivaPrasad)\
**Post date:** [May 4, 2026, 9:23pm UTC](https://community.omni.co/t/create-a-timezone-picker-for-your-end-users/456/4 "2026-05-04T21:23:45Z")

</div>

> [@Jiro](#):
>
> May 1, 2026 - Omni Docs

Oo! That timezone overrides Content permissions looks sick! We’ll wait for that. Meanwhile I’ll also start setting the the user’s timezone in the user attributes. Thanks for that example.