Update documentation to clarify how to set Global Capabilities
The documentation does not clearly state that the Global Capabilities are set via the access rights of the root project (All-Projects). Also the section in which the Global Capabilities are documented is named "System Capabilities" which makes it harder to find by searching. Change the name of the section, and add a clarification paragraph. Change-Id: I46eaf1e81dfc4962f482571fe25b6a6a10e17b45
This commit is contained in:
@@ -1021,11 +1021,11 @@ on `refs/for/refs/heads/<branch>` rather than permissions to upload changes
|
||||
on `refs/heads/<branch>`.
|
||||
|
||||
|
||||
[[system_capabilities]]
|
||||
System capabilities
|
||||
[[global_capabilities]]
|
||||
Global Capabilities
|
||||
-------------------
|
||||
|
||||
The system capabilities control actions that the administrators of
|
||||
The global capabilities control actions that the administrators of
|
||||
the server can perform which usually affect the entire
|
||||
server in some way. The administrators may delegate these
|
||||
capabilities to trusted groups of users.
|
||||
@@ -1036,6 +1036,9 @@ administrative control of the server. This makes it possible to
|
||||
keep fewer users in the administrators group, even while spreading
|
||||
much of the server administration burden out to more users.
|
||||
|
||||
Global capabilities are assigned to groups in the access rights settings
|
||||
of the root project ("`All-Projects`").
|
||||
|
||||
Below you find a list of capabilities available:
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user