DOCS SONAR-14170 Document security hotspot "Open in IDE" feature

diff --git a/server/sonar-docs/src/pages/user-guide/security-hotspots.md b/server/sonar-docs/src/pages/user-guide/security-hotspots.md
index a65be529438f97bb2cd9eb55ba51e7874b65a153..f312d43236ba627e539145fc5cd29670bbfb9e2e 100644 (file)
--- a/server/sonar-docs/src/pages/user-guide/security-hotspots.md
+++ b/server/sonar-docs/src/pages/user-guide/security-hotspots.md
@@ -59,4 +59,16 @@ After following these steps, set the Security Hotspot to one of the following:
 
 ### Review History
 
-The **Review history** tab shows the history of the Security Hotspot including the status it's been assigned and any comments the reviewer had regarding the Hotspot.  
+The **Review history** tab shows the history of the Security Hotspot including the status it's been assigned and any comments the reviewer had regarding the Hotspot.
+
+### Reviewing Hotspots in your IDE
+
+Seeing a Security Hotspot directly in the IDE can help you better understand its context and decide whether it is safe or not. This is the purpose of the **Open in IDE** button that you'll see as an authenticated user.
+
+This feature is available to users of:
+* [SonarLint for Visual Studio](https://www.sonarlint.org/visualstudio) 4.29 and above 
+* [SonarLint for IntelliJ](https://www.sonarlint.org/intellij) 4.13 and above
+
+The project needs to be open in the appropriate IDE and bound to the server through SonarLint's connected mode.
+
+Keep in mind that the revision or branch analyzed by SonarQube may not be the same as what you have opened in the IDE. In this case, SonarLint will do its best to locate the Security Hotspot in your local code.