> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/settings/workspace-timezone.md).

# Workspace Timezone

#### Timezone Standardization — What's Changing

**TL;DR:** TL;DR: After January 12, 2026, all accounts must have an account timezone. If none is set, it will default to UTC (GMT+0).

**Why This Matters**

Currently when workspace timezone isn't set, HockeyStack falls back to each user's browser timezone. This means team members in different locations can see slightly different numbers for the same report, especially around date boundaries.

Setting an account timezone ensures consistent reporting across your entire team. No more mismatches when viewing analytics from different locations.

**What's Changing**

| Before                         | After                        |
| ------------------------------ | ---------------------------- |
| Timezone optional              | Timezone required            |
| Falls back to browser timezone | Falls back to UTC if not set |

**What You Need to Do**

1. Go to [**Settings → Workspace → Reporting & Tracking**](http://app.hockeystack.com/dashboard/settings/workspace?tab=reporting)
2. Set your **Account Timezone**
3. Done.

> ⏰ **Deadline: January 12, 2026**

**What's Affected**

Reports, dashboards, charts, attribution, date groupings, scheduled prompts—anything time-based in HockeyStack.

**Questions?**

Reach out to your CSM or <support@hockeystack.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hockeystack.com/marketing-intelligence/settings/workspace-timezone.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.