DOCS add note about Execute Analysis permissions and private projects

diff --git a/server/sonar-docs/src/pages/instance-administration/security.md b/server/sonar-docs/src/pages/instance-administration/security.md
index b27590cceb56b8b30163968580e77108907990a4..24e5cba9e60f100eee1aedd31413eb2675a92d22 100644 (file)
--- a/server/sonar-docs/src/pages/instance-administration/security.md
+++ b/server/sonar-docs/src/pages/instance-administration/security.md
@@ -132,7 +132,7 @@ To set global permissions, log in as a System administrator and go to **[Adminis
 * **Administer System**: All administration functions for the instance: global configuration.
 * **Administer Quality Profiles**: Any action on Quality Profiles.
 * **Administer Quality Gates**: Any action on quality gates
-* **Execute Analysis**: Execute analyses (project, view, report, developer), and to get all settings required to perform the analysis, even the secured ones like the SCM account password, and so on.
+* **Execute Analysis**:  Access to all settings required to perform analysis and the ability to push analysis results to the SonarQube server. This includes private project settings and secured settings like passwords. 
 * **Create Projects**: Initialize the structure of a new project before its first analysis. This permission is also required when doing the very first analysis of a project that has not already been created via the GUI. * **
 * **Create Applications**: Create a new Application. * **
 * **Create Portfolios**: Create a new Portfolio. * **
@@ -149,7 +149,7 @@ Project visibility may be toggled between public or private. Making a project pr
 * **Administer Issues**: Change the type and severity of issues, resolve issues as being "Won't Fix" or "False Positive" (users also need "Browse" permission).
 * **Administer Security Hotspots**: Change the status of a Security Hotspot.
 * **Administer**: Access project settings and perform administration tasks (users also need "Browse" permission).
-* **Execute Analysis**: Execute analyses (project, view, report, developer), and to get all settings required to perform the analysis, even the secured ones like the SCM account password, the Jira account password, and so on.
+* **Execute Analysis**: Access to all settings required to perform analysis and the ability to push analysis results to the SonarQube server. This includes private project settings and secured settings like passwords
 
 Private projects have two additional permissions:
 * **Browse**: Access a project; browse its measures, issues, and Security Hotspots; perform some issue edits (confirm/resolve/reopen, assignment, comment); comment on or change the user assigned to a Security Hotspot.