From d38190f8c40c17371a9f61eb52a055d103be2e45 Mon Sep 17 00:00:00 2001 From: Anbraten Date: Sat, 26 Feb 2022 13:22:43 +0100 Subject: [PATCH] Update 71-project-settings.md --- docs/docs/20-usage/71-project-settings.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/docs/20-usage/71-project-settings.md b/docs/docs/20-usage/71-project-settings.md index 0ebe372f473..739df512910 100644 --- a/docs/docs/20-usage/71-project-settings.md +++ b/docs/docs/20-usage/71-project-settings.md @@ -22,6 +22,12 @@ Every build initiated by a user (not including the project owner) needs to be ap If you set your project to trusted, a pipeline step and by this the underlying containers gets access to escalated capabilities like mounting volumes. +:::note + +Only server admins can set this option. If you are not a server admin this option wont be shown in your project settings. + +::: + ## Project visibility You can change the visibility of your project by this setting. If a user has access to a project he can see all builds and their logs and artifacts. Settings, Secrets and Registries can only be accessed by owners.