From fed782ecd8bbe53a02c25fbf101dfc5e09794547 Mon Sep 17 00:00:00 2001
From: "sumit shinde ( Roni )"
 <110285294+sumitshinde-84@users.noreply.github.com>
Date: Tue, 4 Aug 2026 16:32:36 +0530
Subject: [PATCH] Fix the mcp audit log section url

---
 docs/user/expert/chat.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/user/expert/chat.md b/docs/user/expert/chat.md
index 58654b7a17..63592c0d0f 100644
--- a/docs/user/expert/chat.md
+++ b/docs/user/expert/chat.md
@@ -135,7 +135,7 @@ The settings split actions into two groups: **Flow Building Tools**, the actions
 
 **Role-based limits.** Permissions respect your team role. Read-only team members cannot enable or trigger actions that write or delete, and will see why they are unavailable. This is enforced by Expert itself, not just hidden in the interface.
 
-**Auditability.** Every action Expert takes on the platform is recorded in the [Audit Log](/docs/user/logs.md#mcp-and-api-activity), alongside the tool it called and the user it was acting on behalf of.
+**Auditability.** Every action Expert takes on the platform is recorded in the [Audit Log](/docs/user/logs.md#ai-agents-and-api-activity), alongside the tool it called and the user it was acting on behalf of.
 
 **Example permission setups.** A few common ways to configure this: