Merge pull request #1344 from silentoplayz/fix/per-chat-tools-integrations-menu

docs: correct per-chat tool enabling to the Integrations menu

Author: Classic298

docs/features/extensibility/mcp.mdx

@@ -141,7 +141,7 @@ No configuration is needed on the Open WebUI side: the resource indicator is dis
 
 If an OAuth 2.1 tool is set as a default and the user hasn't previously authenticated (or their refresh token has expired), the tool call will fail with **"Failed to connect to MCP server"** because the backend cannot initiate the browser-based auth flow mid-request.
 
-**Workaround:** Users should manually enable OAuth 2.1 tools per-chat via the **➕** button in the chat input area. This triggers the auth flow before the tool is ever invoked. Token refresh works automatically once the initial authentication is complete.
+**Workaround:** Users should manually enable OAuth 2.1 tools per-chat via the **Integrations** menu in the chat input area. This triggers the auth flow before the tool is ever invoked. Token refresh works automatically once the initial authentication is complete.
 :::
 
 ### Connection URLs

docs/features/extensibility/plugin/tools/index.mdx

@@ -83,7 +83,7 @@ Never import a Tool you don’t recognize or trust. These are Python scripts and
 🔧 Once installed or connected, here’s how to enable them for your conversations:
 
 ### Option 1: Enable on-the-fly (Specific Chat)
-While chatting, click the **➕ (plus)** icon in the input area. You’ll see a list of available Tools, and you can enable them specifically for that session.
+While chatting, click the **Integrations** icon in the input area (the four-diamond icon next to the ➕ button), then select **Tools**. You’ll see a list of available Tools, and you can toggle them on specifically for that session.
 
 ### Option 2: Enable by Default (Global/Model Level)
 1. Go to **Workspace ➡️ Models**.

docs/features/extensibility/plugin/tools/openapi-servers/open-webui.mdx

@@ -151,15 +151,15 @@ If you've connected a Global Tool Server (i.e., one that's admin-configured), it
 Instead:
 
 - Global tools are hidden by default and must be explicitly activated per user.
-- To enable them, you'll need to click on the ➕ button in the message input area (bottom left of the chat box), and manually toggle on the specific global tool(s) you want to use.
+- To enable them, you'll need to click on the **Integrations** button in the message input area (bottom left of the chat box, next to the ➕ button), select **Tools**, and manually toggle on the specific global tool(s) you want to use.
 
 Here's what that looks like:
 
 ![Global Tool Server Message Input](/images/openapi-servers/open-webui/global-message-input.png)
 
 ⚠️ Important Notes for Global Tool Servers:
 
-- They will not show up in the tool indicator popup until enabled from the ➕ menu.
+- They will not show up in the tool indicator popup until enabled from the **Integrations** menu.
 - Each global tool must be individually toggled on to become active inside your current chat.
 - Once toggled on, they function the same way as user tools.
 - Admins can control access to global tools via role-based permissions.