SONAR-15883 Explain Portfolio permissions

diff --git a/server/sonar-docs/src/pages/project-administration/managing-portfolios.md b/server/sonar-docs/src/pages/project-administration/managing-portfolios.md
index 1a6c3d4810db7ba9d0be0598fee67e872331fbb6..25e70e132282fe564d464541b772db5de0b4a334 100644 (file)
--- a/server/sonar-docs/src/pages/project-administration/managing-portfolios.md
+++ b/server/sonar-docs/src/pages/project-administration/managing-portfolios.md
@@ -18,6 +18,9 @@ Users with the Create Portfolios permission and global administrators can create
 ### Editing Portfolios
 Users need to have either **Administer** permissions for any Portfolios that they want to edit or the global **Administer System** permission.
 
+[[info]]
+|Giving a user **Administer** permission to an existing portfolio that was created using manual selection allows that user to see all project names and keys for the projects in the Portfolio, even if the user doesn't have access to those projects.
+
 ## Populating Portfolios
 After you've created a portfolio, you can populate it with projects, applications, and other portfolios.