merge + final tweaks

docs/documentation/platform/access-controls/access-requests.mdx

@@ -3,10 +3,10 @@ title: "Access Requests"
 description: "Learn how to request access to sensitive resources in Infisical."
 ---
 
-In certain situations, developers need to expand their access to a certain new project or a sensitive environment. For those use cases, it is helpful to utilize Infisical's **Access Requests** functionality. 
+In certain situations, developers need to expand their access to a certain new project or a sensitive environment. For those use cases, it is helpful to utilize Infisical's **Access Requests** functionality.
 
-This functionality works in the following way: 
-1. A project administrator sets up an access policy that assigns access managers (also known as eligible approvers) to a certain sensitive folder or environment. 
+This functionality works in the following way:
+1. A project administrator sets up an access policy that assigns access managers (also known as eligible approvers) to a certain sensitive folder or environment.
 ![Create Access Request Policy Modal](/images/platform/access-controls/create-access-request-policy.png)
 ![Access Request Policies](/images/platform/access-controls/access-request-policies.png)
 
@@ -19,9 +19,8 @@ This functionality works in the following way:
 ![Access Request Bypass](/images/platform/access-controls/access-request-bypass.png)
 
 <Info>
- If the access request matches with a policy that has a **Soft** enforcement level, the requester may bypass the policy and get access to the resource without full approval.
+ If the access request matches with a policy that has allows break-glass approval bypasses, the requester may bypass the policy and get access to the resource without full approval.
 </Info>
 
-5. As soon as the request is approved, developer is able to access the sought resources. 
+5. As soon as the request is approved, developer is able to access the sought resources.
 ![Access Request Dashboard](/images/platform/access-controls/access-requests-completed.png)
-

docs/documentation/platform/pr-workflows.mdx

@@ -33,6 +33,8 @@ First, you would need to create a set of policies for a certain environment. In
 
 The enforcement level determines how strict the policy is. A **Hard** enforcement level means that any change that matches the policy will need full approval prior merging. A **Soft** enforcement level allows for break glass functionality on the request. If a change request is bypassed, the approvers will be notified via email.
 
+You can use the **Soft** enforcement level by enabling "Bypass Approvals".
+
 ### Self approvals
 
 If the **Self Approvals** option is enabled, users who are designated as approvers on the policy can approve requests that they themselves have submitted.

docs/internals/permissions/project-permissions.mdx

@@ -185,6 +185,7 @@ Supports conditions and permission inversion
 | `edit`                | Modify approval policies                                                     |
 | `delete`              | Remove approval policies                                                     |
 | `allow-change-bypass` | Allow request creators to bypass policy in break-glass situations            |
+| `allow-access-bypass` | Allow request creators to bypass policy in break-glass situations            |
 
 #### Subject: `secret-rotation`