diff --git a/docs/getting-started/which-permissions-does-codacy-need-from-my-account.md b/docs/getting-started/which-permissions-does-codacy-need-from-my-account.md
index eb15a13529..b6b40b9186 100644
--- a/docs/getting-started/which-permissions-does-codacy-need-from-my-account.md
+++ b/docs/getting-started/which-permissions-does-codacy-need-from-my-account.md
@@ -67,6 +67,11 @@ If you log in with GitHub, Codacy requires the following [app permissions](https
       <td>Read-Only</td>
       <td>Codacy retrieves repository contents to get installation access tokens when integrating with your repositories and clone them, and for code coverage analysis.<br/><strong>Codacy requests this permission since September 2023.</strong> Make sure an organization owner <a href="https://docs.github.com/en/apps/using-github-apps/reviewing-and-modifying-installed-github-apps">approves Codacy GitHub App updated permissions</a> on your GitHub organization.</td>
     </tr>
+    <tr>
+      <td>Merge groups</td>
+      <td>Read-Only</td>
+      <td>Codacy listens for the `merge_group` webhook event and responds to the `checks_requested` action accordingly.</td>
+    </tr>
     <tr>
       <td colspan="3"><strong>Organization permissions:</strong></td>
     </tr>
diff --git a/docs/repositories-configure/integrations/github-integration.md b/docs/repositories-configure/integrations/github-integration.md
index 2155ac78e1..6b01ccf443 100644
--- a/docs/repositories-configure/integrations/github-integration.md
+++ b/docs/repositories-configure/integrations/github-integration.md
@@ -90,6 +90,12 @@ Adds comments on the lines of the pull request where Codacy finds new issues wit
 
 ![Comment suggesting a fix on GitHub](images/github-integration-suggest-fixes.png)
 
+## Merge queues {: id="merge-queues"}
+
+To support GitHub **merge queues**, our GitHub App requires **Merge Groups** permissions so it can listen for and respond to the `checks_requested` action for merge group events.
+
+When a merge group event is triggered for a pull request in the merge queue, Codacy automatically sends a green status check for **Codacy Static Code Analysis** to the relevant commit. By the time a pull request enters the merge queue, it has already gone through Codacy's analysis — either receiving a green status or being manually bypassed. Since the pull request was already unblocked before joining the queue, always responding with green is a safe and practical approach that keeps things moving without unnecessary friction.
+
 ## See also
 
 -   [Integrating Codacy with your Git workflow](../../getting-started/integrating-codacy-with-your-git-workflow.md)