Tidy up documentation of the "Submit (On Behalf Of)" permission
The documentation refers to "SubmitAs", but the permission is actually
named "Submit (On Behalf Of). Update the documentation to refer to the
correct name.
Move the documentation of the permission to its own section, rather
than only mentioning it inside the "Submit" section.
Change-Id: I9c8deb3506a72ca614e6419157d5b1bed594e176
diff --git a/Documentation/access-control.txt b/Documentation/access-control.txt
index 688f637..f73600a 100644
--- a/Documentation/access-control.txt
+++ b/Documentation/access-control.txt
@@ -753,10 +753,7 @@
Submitting a change causes it to be merged into the destination
branch as soon as possible, making it a permanent part of the
-project's history. There is also a `SubmitAs` permission that enables
-submitting on behalf of another user. To be able to submit on behalf of
-another user the caller must have been granted both `Submit` and
-`SubmitAs` permission.
+project's history.
In order to submit, all labels (such as `Verified` and `Code-Review`,
above) must enable submit, and also must not block it. See above for
@@ -766,6 +763,14 @@
the caller needs to have the Submit permission on `refs/for/<ref>`
(e.g. on `refs/for/refs/heads/master`).
+[[category_submit_on_behalf_of]]
+=== Submit (On Behalf Of)
+
+This category permits users who have also been granted the `Submit`
+permission to submit changes on behalf of another user.
+
+Note that this permission is named `submitAs` in the `project.config`
+file.
[[category_view_drafts]]
=== View Drafts
diff --git a/Documentation/rest-api-changes.txt b/Documentation/rest-api-changes.txt
index b9060f8..036392c 100644
--- a/Documentation/rest-api-changes.txt
+++ b/Documentation/rest-api-changes.txt
@@ -3287,12 +3287,12 @@
|`on_behalf_of`|optional|
The link:rest-api-accounts.html#account-id[\{account-id\}] of the user on
whose behalf the action should be done. To use this option the caller must
-have been granted both `Submit` and `SubmitAs` permission. The user named
-by `on_behalf_of` does not need to be granted `Submit` permissions. This
-feature is aimed for CI solutions: the CI account can be granted both
-permssions, so individual users don't need `Submit` permission themselves.
-Still the changes can be submited on behalf of real users and not with the
-identity of the CI account.
+have been granted both `Submit` and `Submit (On Behalf Of)` permissions.
+The user named by `on_behalf_of` does not need to be granted the `Submit`
+permission. This feature is aimed for CI solutions: the CI account can be
+granted both permssions, so individual users don't need `Submit` permission
+themselves. Still the changes can be submited on behalf of real users and
+not with the identity of the CI account.
|==========================
[[submit-input]]
