diff --git a/website/docs/reference/change-requests.mdx b/website/docs/reference/change-requests.mdx
index 522abd6311c2..c493210d6a46 100644
--- a/website/docs/reference/change-requests.mdx
+++ b/website/docs/reference/change-requests.mdx
@@ -13,10 +13,10 @@ import VideoContent from '@site/src/components/VideoContent.jsx';
 ## Overview
 
 Change requests allow you to require an additional approval step before any changes can be made in an environment. This functionality supports the "four-eyes principle", ensuring compliance in industries with strict legal or regulatory requirements.
- 
+
 Change requests also allow you to group changes and [apply them at a specific point in time](#scheduled-change-requests).
 
-Change requests can be enabled on a per-project and per-environment basis. This allows you to differentiate your configurations across different environments, such as production and development.
+Change requests can be enabled for a specific environment within a project, or configured globally for an environment across all projects. This allows you to differentiate your configurations across different environments, such as production and development.
 
 You can require up to 10 approvals for a change request.
 
@@ -78,7 +78,7 @@ Alternatively, you can use constraints or segments with the `DATE_AFTER` [operat
 ### Scheduling errors
 
 Unleash suspends a scheduled change request if:
-- The change request includes updates to a flag that has been archived or a strategy that has been deleted. 
+- The change request includes updates to a flag that has been archived or a strategy that has been deleted.
 - The change request includes a strategy, segment, or variant that has been updated.
 - The user who scheduled a change request is deleted from the users list before the scheduled time.
 
@@ -104,8 +104,27 @@ While change requests are environment-specific, project segments are not. For th
 
 Only Admin users can bypass the change request process for project segments through API calls.
 
+## Environment-level change requests
+
+:::note Availability
+
+**Plan**: [Enterprise](https://www.getunleash.io/pricing) | **Version**: `6.10+`
+
+:::
+
+You can preconfigure change request requirements at the environment level. When configured, all new projects automatically inherit these approval requirements for the specified environments.
+
+You can use environment-level change requests in two ways:
+
+* **As defaults**: Set default approvals per environment, but allow project [Owners](/reference/rbac#projects#predefined-roles) and users with [project update permissions](/reference/rbac#projects) to override the defaults within their projects.
+* **As enforced requirements**: Set mandatory approvals for a given environment across all projects. To fully enforce this in a project, ensure that the project has no Owner or users with project update permissions—this prevents any change request modifications at the project level.
+
+You can predefine environment-level change requests when creating or editing an environment in **Configure > Environments**.
+
+![Environment-level change requests](/img/environment-level-change-requests.png)
+
 ## Change request preview
 
 To verify a change request, you can preview the changes in [Playground](/reference/playground) by clicking **Preview changes**. You can adjust [Unleash context](/reference/playground#the-unleash-context), but the project and environment remain fixed as they are determined by the change request.
 
-You can only preview a change request in **In Review**, **Approved**, or **Scheduled** states.
\ No newline at end of file
+You can only preview a change request in **In Review**, **Approved**, or **Scheduled** states.
diff --git a/website/static/img/environment-level-change-requests.png b/website/static/img/environment-level-change-requests.png
new file mode 100644
index 000000000000..f303a670e23e
Binary files /dev/null and b/website/static/img/environment-level-change-requests.png differ