diff --git a/platform-enterprise_docs/enterprise/install-studios.md b/platform-enterprise_docs/enterprise/install-studios.md
index b208de951..c88052ec5 100644
--- a/platform-enterprise_docs/enterprise/install-studios.md
+++ b/platform-enterprise_docs/enterprise/install-studios.md
@@ -45,21 +45,7 @@ Studios uses the following set of domains and subdomains:
 
 ## Studios workspace availability
 
-You can configure which organizational workspaces have access to Studios. This configuration is set in the `tower.yml` file. The `tower.data-studio.allowed-workspaces` field supports the following options:
-
-- `allowed-workspaces: []`: Disables Studios. This is the default if the `allowed-workspaces` field is not specified.
-- `allowed-workspaces: [ <WORKSPACE_ID>,<WORKSPACE_ID> ]`: Enables Studios for the comma-separated list of organizational workspace IDs.
-- `allowed-workspaces: null`: Enables Studios for all organizational workspaces.
-
-In the Platform Helm chart, set the desired configuration in the `platform.YAMLConfigFileContent` field. For example, to enable Studios for workspaces 12345 and 67890:
-
-```yaml
-platform:
-  YAMLConfigFileContent: |-
-    tower:
-      data-studio:
-        allowed-workspaces: [12345,67890]
-```
+You can configure which organizational workspaces have access to Studios by setting the `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` environment variable on the backend containers. By default, all workspaces have access to Studios. To restrict access to specific workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` to a comma-separated list of workspace names. For example, `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES="12345,67890"` allows only the workspaces named `12345` and `67890` to access Studios. To disable access to Studios for all workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES=""` (an empty string).
 
 ## Available Studios environment images
 
diff --git a/platform-enterprise_docs/enterprise/studios-docker-compose.md b/platform-enterprise_docs/enterprise/studios-docker-compose.md
index 38dd77437..11e6f829d 100644
--- a/platform-enterprise_docs/enterprise/studios-docker-compose.md
+++ b/platform-enterprise_docs/enterprise/studios-docker-compose.md
@@ -60,21 +60,7 @@ Other than the basic requirements [already listed in the Studios installation ov
     - `TOWER_OIDC_REGISTRATION_INITIAL_ACCESS_TOKEN`: The same value as `oidc_registration_token`.
     - `TOWER_OIDC_PEM_PATH`: The file path to the PEM certificate (e.g., `/data-studios-rsa.pem`).
 
-1. Edit the `tower.yml` file and include the following snippet to enable Studios in all workspaces in your Platform instance:
-
-    ```yaml
-    tower:
-      data-studio:
-        allowed-workspaces: null
-    ```
-
-    Alternatively, you can specify a comma-separated list of workspace IDs to enable Studios only on those workspaces.
-
-    ```yaml
-    tower:
-      data-studio:
-        allowed-workspaces: [12345,67890]
-    ```
+1. From Platform v26.1, Studios is enabled by default on all workspaces. To enable Studios on specific workspaces only, set the `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` environment variable (e.g., `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES="12345,67890"`) on the Platform backend containers. To disable Studios for all workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES=""` (an empty string).
 
 1. Start your Platform instance:
 
diff --git a/platform-enterprise_docs/enterprise/studios-kubernetes.md b/platform-enterprise_docs/enterprise/studios-kubernetes.md
index ae2a9a81a..132282760 100644
--- a/platform-enterprise_docs/enterprise/studios-kubernetes.md
+++ b/platform-enterprise_docs/enterprise/studios-kubernetes.md
@@ -102,23 +102,7 @@ You can also check the current template configuration using `https://towerurl/ap
    - `TOWER_DATA_STUDIO_CONNECT_URL`: The URL of the Studios connect proxy, such as `https://connect.example.com/`.
    - `TOWER_OIDC_REGISTRATION_INITIAL_ACCESS_TOKEN`: The same value as the `oidc_registration_token` value created previously.
 
-1. Edit the ConfigMap named `tower-yml` in the `configmap.yml` and include the following snippet:
-
-    ```yaml
-    data:
-      tower.yml: |-
-        tower:
-          data-studio:
-            allowed-workspaces: null
-    ```
-
-    Alternatively, you can specify a comma-separated list of workspace IDs to enable Studios only on those workspaces.
-
-    ```yaml
-    tower:
-      data-studio:
-        allowed-workspaces: [12345,67890]
-    ```
+1. From Platform v26.1, Studios is enabled by default on all workspaces. To enable Studios on specific workspaces only, set the `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` environment variable (e.g., `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES="12345,67890"`) on the Platform backend containers. To disable Studios for all workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES=""` (an empty string).
 
 1. Apply the updated configuration: