diff --git a/embed/iframe.mdx b/embed/iframe.mdx
index f4da5d4b..83261c0c 100644
--- a/embed/iframe.mdx
+++ b/embed/iframe.mdx
@@ -242,7 +242,7 @@ https://app.lightdash.cloud/embed/abc-123?backgroundColor=1c1c1c#eyJhbGci...
### `timezone`
-Beta Contact support to enable the embed `timezone` param for your organization. While it is off, the param is ignored and the session falls back to the chart pin or project default. [What Beta means](/support/feature-maturity-levels).
+Beta The embed `timezone` param is available to all organizations. On self-hosted instances where timezone support is disabled with `LIGHTDASH_ENABLE_TIMEZONE_SUPPORT=false`, the param is ignored and the session falls back to the chart pin or project default. [What Beta means](/support/feature-maturity-levels).
Sets a per-session query timezone for the embed. Use it when one embedded dashboard needs to render in different timezones for different viewers (for example, a multi-tenant app where each tenant has its own timezone), without creating separate charts per timezone.
diff --git a/semantic-layer/dimensions.mdx b/semantic-layer/dimensions.mdx
index 860e27a0..f7c04625 100644
--- a/semantic-layer/dimensions.mdx
+++ b/semantic-layer/dimensions.mdx
@@ -174,7 +174,7 @@ The table below shows all the dimension properties you can customize:
| [case_sensitive](#case-sensitive) | No | boolean | If set to `false`, string filters on this dimension will be case insensitive. Defaults to `true`. Overrides explore-level setting. |
| [filter_autocomplete](#filter-autocomplete) | No | Object | Configure the filter autocomplete suggestions for this dimension. Provide a static list of `values` (with optional display `label`s), point at a `label_dimension` in the same table to label warehouse-fetched values, source values from a dimension in another model with `options_from_dimension`, and/or disable warehouse-based autocomplete by setting `fetch_from_warehouse: false`. |
| [tags](#tags) | No | string[] | An array of string tags for categorizing and filtering dimensions programmatically. Tags can be used by AI agents, API filters, and other backend workflows. |
-| [convert_timezone](#convert-timezone) | No | boolean | **[Experimental]** If set to `false`, the dimension opts out of the project query timezone for display, grouping, and extracts - the raw warehouse value is rendered instead. Defaults to `true`. Has no effect unless a project query timezone is set. |
+| [convert_timezone](#convert-timezone) | No | boolean | If set to `false`, the dimension opts out of the project query timezone for display, grouping, and extracts - the raw warehouse value is rendered instead. Defaults to `true`. Has no effect unless a project query timezone is set. |
| [timestamp_domain](#timestamp-domain) | No | `aware` or `naive` | Declares whether a `timestamp` column stores an instant (`aware`) or a bare wall clock with no zone (`naive`). Overrides what Lightdash detects from the warehouse catalog. |
@@ -1156,7 +1156,7 @@ Lightdash dimensions and custom metrics are protected by this feature, however,
## Convert timezone
- Experimental Contact support to enable the `convert_timezone` dimension override for your organization. It has no effect unless the [project query timezone](/workspace-admin/set-project-timezone#configure-your-project-timezone) is set. [What Experimental means](/support/feature-maturity-levels).
+ `convert_timezone` has no effect unless the [project query timezone](/workspace-admin/set-project-timezone#configure-your-project-timezone) is set.
Set `convert_timezone: false` on a `timestamp` dimension to opt it out of the project query timezone. This is useful for columns that should always render in their raw warehouse value - system timestamps, audit logs, or pre-converted timezone columns.