diff --git a/.github/workflows/claude-issue-labeler.yml b/.github/workflows/claude-issue-labeler.yml
index fcc83bf4f3..f26c511453 100644
--- a/.github/workflows/claude-issue-labeler.yml
+++ b/.github/workflows/claude-issue-labeler.yml
@@ -30,6 +30,7 @@ jobs:
         with:
           anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
           github_token: ${{ secrets.GITHUB_TOKEN }}
+          allowed_non_write_users: '*'
           prompt: |
             Call the security screening skill:
             /identify-security-vuln-discussion
@@ -60,6 +61,7 @@ jobs:
         with:
           anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
           github_token: ${{ secrets.GITHUB_TOKEN }}
+          allowed_non_write_users: '*'
           prompt: |
             Call the code of conduct check skill:
             /code-of-conduct-check
@@ -83,6 +85,7 @@ jobs:
         with:
           anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
           github_token: ${{ secrets.GITHUB_TOKEN }}
+          allowed_non_write_users: '*'
           prompt: |
             Call the label assignment skill:
             /assign-label
@@ -111,6 +114,12 @@ jobs:
             exit 0
           fi
 
+          # Skip codeowner notification for KB PR review tracking issues
+          if echo "$LABELS" | grep -q "kb/review"; then
+            echo "Issue has kb/review label — skipping codeowner notification"
+            exit 0
+          fi
+
           # Read the mapping file
           MAPPING=$(cat .github/label-codeowners.json)
 
diff --git a/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/AuthPPEdcagent.png b/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/AuthPPEdcagent.png
new file mode 100644
index 0000000000..20e11b0d65
Binary files /dev/null and b/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/AuthPPEdcagent.png differ
diff --git a/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/PPEAuth0.png b/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/PPEAuth0.png
new file mode 100644
index 0000000000..4a8785218e
Binary files /dev/null and b/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/PPEAuth0.png differ
diff --git a/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/dcagentAuth0.png b/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/dcagentAuth0.png
new file mode 100644
index 0000000000..8df76d7fee
Binary files /dev/null and b/docs/kb/passwordpolicyenforcer/authentication-and-integration/0-images/dcagentAuth0.png differ
diff --git a/docs/kb/passwordpolicyenforcer/authentication-and-integration/subauthentication-filter-conflict-when-fortinet-and-password-policy-enforcer.md b/docs/kb/passwordpolicyenforcer/authentication-and-integration/subauthentication-filter-conflict-when-fortinet-and-password-policy-enforcer.md
new file mode 100644
index 0000000000..c1b3b16e64
--- /dev/null
+++ b/docs/kb/passwordpolicyenforcer/authentication-and-integration/subauthentication-filter-conflict-when-fortinet-and-password-policy-enforcer.md
@@ -0,0 +1,63 @@
+---
+description: >-
+  When Password Policy Enforcer (PPE) Server and Fortinet are installed on the same Domain Controller, Fortinet can take over the SubAuthentication registry value, which will prevent PPE from informing Windows to display password expiry notifications. This article explains the cause and provides registry edits to restore PPE functionality.
+keywords:
+  - Netwrix Password Policy Enforcer
+  - Fortinet
+  - registry
+  - PPE
+  - Windows Registry
+  - SubAuthentication
+  - Auth0
+  - subauthentication filter
+
+products:
+  - passwordpolicyenforcer
+sidebar_label: SubAuthentication Filter Event Warning When Fortinet Is Installed
+tags:
+  - kb
+  - authentication-and-integration
+title: "SubAuthentication Filter Event Warning When Fortinet Is Installed"
+knowledge_article_id: ""
+---
+
+# SubAuthentication Filter Event Warning When Fortinet Is Installed
+
+## Symptom
+
+Event ID 2060 appears in the event logs when Netwrix Password Policy Enforcer (PPE) and Fortinet are both installed on the same Domain Controllers:
+
+```
+Event ID 2060 (Warning)
+Netwrix Password Policy Enforcer is not prompting users to change passwords that are approaching their expiry date because another application has installed its own subauthentication filter. You can configure the app to use both filters concurrently.
+```
+
+## Cause
+
+Fortinet removes PPE from the SubAuthentication Filter value (`Auth0`) in the following registry key:
+- `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\`. 
+
+This prevents PPE from informing Windows to display password expiry notifications on the client computer. 
+
+## Resolution
+
+Only the maximum age rule of PPE uses the SubAuthentication Filter (`Auth0`) to display the **Your password expires in [n] days** notification on the client computer. PPE sets the password expiry time in the Kerberos ticket on the Domain Controller and does not rely on the PPE client. PPE does not use the subauthentication filter for any rule enforcement.
+
+> **NOTE:** Alternatively, use Windows to enforce the maximum age or configure PPE reminder emails.
+
+To restore the password expiry reminder when PPE and Fortinet are both installed, make the following registry edits:
+
+1.	Open `RegEdit` to key: `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\`.
+2.	Verify that the `Auth0` registry value reads `dcagent`.
+
+	![Registry editor showing the Auth0 value set to dcagent](./0-images/dcagentAuth0.png)
+
+3.	Set the `Auth0` value to `PPE`.
+
+	![Registry editor showing the Auth0 value set to PPE](./0-images/PPEAuth0.png)
+
+4.	Create a new value of type `REG_SZ` called `AuthPPE`, and set it to `dcagent`.
+
+	![Registry editor showing the new AuthPPE value set to dcagent](./0-images/AuthPPEdcagent.png)
+
+5.	Restart the Domain Controller.