> Documentation index: https://www.gooddata.ai/docs/gooddata-ui/llms.txt lists every page of these docs as Markdown.

# changeDashboardTimezoneOverride()

- Package: [@gooddata/sdk-ui-dashboard](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/index.md)
- Kind: function
- Stability: alpha
- Source: https://github.com/gooddata/gooddata-ui-sdk/blob/rel/11.64/libs/sdk-ui-dashboard/src/model/commands/timezone.ts

> **Alpha API.** Initial API, highly likely to change outside SemVer. Don't build on it in production. See [API maturity](https://www.gooddata.ai/docs/gooddata-ui/latest/integrations/platform/api-maturity/index.md).
> 

Creates the ChangeDashboardTimezoneOverride command.

**Signature:**

```typescript
export declare function changeDashboardTimezoneOverride(timezoneId: string | undefined, correlationId?: string, bypassUserOverrideCheck?: boolean): IChangeDashboardTimezoneOverride;
```

## Parameters

| Parameter | Type | Description |
| --- | --- | --- |
| timezoneId | string \| undefined | concrete IANA timezone id, the BROWSER\_DETECTED sentinel (resolved to the viewer's browser timezone by the handler), or undefined to clear the override |
| correlationId | string | _(Optional)_ specify correlation id to use for this command. this will be included in all events that will be emitted during the command processing |
| bypassUserOverrideCheck | boolean | _(Optional)_ see [IChangeDashboardTimezoneOverridePayload.bypassUserOverrideCheck](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.ichangedashboardtimezoneoverridepayload/index.md#ichangedashboardtimezoneoverridepayloadbypassuseroverridecheck) |

**Returns:**

[IChangeDashboardTimezoneOverride](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.ichangedashboardtimezoneoverride/index.md)

## Remarks

Dispatching this command will set (or clear, when timezoneId is undefined) the session-only ad-hoc timezone override of the dashboard. The override takes precedence over the dashboard's configured timezone, is never persisted with the dashboard, and resets on full reload.

The command is rejected when the ad-hoc override is not allowed: the dashboard timezone feature is disabled or the dashboard's timezone configuration does not allow user overrides in view mode — the latter bypassable via `bypassUserOverrideCheck`.