Update codeowners docs with access restrictions note

doc/user/project/code_owners.md

@@ -80,6 +80,14 @@ Once set, Code Owners are displayed in merge requests widgets:
 NOTE: **Note**:
   While the`CODEOWNERS` file can be used in addition to Merge Request [Approval Rules](merge_requests/merge_request_approvals.md#approval-rules) it can also be used as the sole driver of a Merge Request approval (without using  [Approval Rules](merge_requests/merge_request_approvals.md#approval-rules)) by simply creating the file in one of the three locations specified above, configuring the Code Owners to be required approvers for [protected branches](protected_branches.md#protected-branches-approval-by-code-owners-premium) and then using [the syntax of Code Owners files](code_owners.md#the-syntax-of-code-owners-files) to specify the actual owners and granular permissions.
 
+NOTE: **Note**:
+  Using Code Owners in conjunction with [Protected Branches Approvals](protected_branches.md#protected-branches-approval-by-code-owners-premium)
+  will prevent any user who is not specified in the `CODEOWNERS` file from pushing changes
+for the specified files/paths, even if their role is included in the **Allowed to push** column.
+This allows for a more inclusive push strategy, as administrators don't have to restrict developers
+  from pushing directly to the protected branch, but can restrict pushing to certain
+files where a review by Code Owners is required.
+
 ## The syntax of Code Owners files
 
 Files can be specified using the same kind of patterns you would use