diff --git a/website/docs/user_guide/environments.md b/website/docs/user_guide/environments.md
index 63f53e4d3f..d10892ed10 100644
--- a/website/docs/user_guide/environments.md
+++ b/website/docs/user_guide/environments.md
@@ -3,11 +3,21 @@ id: environments
title: Environments
---
-Environments is a new way to organize activation strategy configurations for feature toggles into separate environments. In Unleash a feature lives across all your environments, after all, the goal is to get the new feature released as soon as possible, but it makes sense to configure the activation differently per environment.
+
+ Environment is a new feature currently under beta. It can be enabled from Unleash v4.2.x behind with a feature toggle. The plan to make the environment feature general available from Unleash v4.3.x.
+
+
+
+
+
+
+
+
+Environments is a new way to organize activation strategy configurations for feature toggles into separate environments. In Unleash a feature lives across all your environments, after all, the goal is to get the new feature released as soon as possible. But it makes sense to configure the activation differently per environment. You might want the feature enabled for everyone in development, while only enable it for yourself in production.
Unleash Enterprise users have been able to leverage strategy constraints to control the roll-out per environment. This will not be needed after the release as a "full group" of activation strategy will belong to an environment.
-Connected applications will also use environment specific API keys, to make sure they only download feature toggle configurations for the environment they are running in.
+Connected applications will also use environment scoped API keys, to make sure they only download feature toggle configurations for the environment they are running in.
Metrics has also been upgraded to record the environment, so that Unleash now can display the usage metrics per environment.