Use the current settings layout and the current control names

Version 0.11 merged the admin area into the settings sidebar, so reaching an admin page is Settings then Admin then the section, rather than opening a separate Admin Panel and then its Settings tab. Pages describing the older route sent readers looking for a step that no longer exists, and the two forms were mixed across the documentation. The API keys page, the three text-to-speech integrations, the Google Drive step in the retrieval guide, four web search providers and the Open Terminal connection guide now all use the current path.

The MCP setup steps also said to click Add Server, which is now Add Connection, and named no section on a page that holds several. Both occurrences now say to use the External Tool Servers section and point out that the page carries more than one.

Author: Classic298

docs/features/authentication-access/api-keys.md

@@ -45,7 +45,7 @@ A key can be replaced or removed outright. Creating a new key overwrites the old
 ### Step 1: Enable API Keys Globally (Admin)
 
 1. Log in as an **administrator**
-2. Open **Admin Panel > Settings > Authentication**
+2. Open **Settings > Admin > Authentication**
 3. Toggle **API Keys** on
 4. Click **Save**
 
@@ -171,7 +171,7 @@ Retiring an integration for good is a **Delete** rather than a rotation, since t
 
 **No API keys section at all in Settings > Account?**
 
-- **Check the global toggle:** verify that an admin has enabled API keys in **Admin Panel > Settings > Authentication**. See [`ENABLE_API_KEYS`](/reference/env-configuration#enable_api_keys).
+- **Check the global toggle:** verify that an admin has enabled API keys in **Settings > Admin > Authentication**. See [`ENABLE_API_KEYS`](/reference/env-configuration#enable_api_keys).
 - **Check your permissions (non-admin users):** verify that your account or group has the **API Keys** feature permission under **Features Permissions**. See [`USER_PERMISSIONS_FEATURES_API_KEYS`](/reference/env-configuration#user_permissions_features_api_keys).
 
 **Getting `401 Unauthorized` responses?**

docs/features/chat-conversations/audio/text-to-speech/Kokoro-FastAPI-integration.md

@@ -112,7 +112,7 @@ services:
 
 To use Kokoro-FastAPI with Open WebUI, follow these steps:
 
-- Open the Admin Panel and go to `Settings` -> `Audio`
+- Go to `Settings` -> `Admin` -> `Audio`
 - Set your TTS Settings to match the following:
 - - Text-to-Speech Engine: OpenAI
   - API Base URL: `http://localhost:8880/v1` # you may need to use `host.docker.internal` instead of `localhost`

docs/features/chat-conversations/audio/text-to-speech/chatterbox-tts-api-integration.md

@@ -207,7 +207,7 @@ We recommend running with the frontend interface so you can upload the audio fil
 
 To use Chatterbox TTS API with Open WebUI, follow these steps:
 
-- Open the Admin Panel and go to `Settings` -> `Audio`
+- Go to `Settings` -> `Admin` -> `Audio`
 - Set your TTS Settings to match the following:
 - - Text-to-Speech Engine: OpenAI
   - API Base URL: `http://localhost:4123/v1` # alternatively, try `http://host.docker.internal:4123/v1`

docs/features/chat-conversations/audio/text-to-speech/openai-edge-tts-integration.md

@@ -49,7 +49,7 @@ This will run the service at port 5050 with all the default configs
 
 ## Setting up Open WebUI to use `openai-edge-tts`
 
-- Open the Admin Panel and go to `Settings` -> `Audio`
+- Go to `Settings` -> `Admin` -> `Audio`
 - Set your TTS Settings to match the screenshot below
 - *Note: you can specify the TTS Voice here*
 

docs/features/chat-conversations/rag/index.md

@@ -382,4 +382,4 @@ When paired with a Google Cloud project that has the Google Picker API and Googl
 10. Set up the environment variable `GOOGLE_DRIVE_API_KEY` to the API Key value setup up in step 7 (NOT the OAuth client secret from step 2).
 11. Set up the `GOOGLE_REDIRECT_URI` to my Open-WebUI instance's URL (include the port, if any).
 12. Then relaunch your Open-WebUI instance with those three environment variables.
-13. After that, make sure Google Drive was enabled under `Admin Panel` < `Settings` < `Documents` < `Google Drive`
+13. After that, make sure Google Drive was enabled under `Settings` > `Admin` > `Documents` > `Google Drive`

docs/features/chat-conversations/web-search/providers/bing.md

@@ -33,7 +33,7 @@ Bing Search APIs will be retired on 11th August 2025. New deployments are not su
 
 1. Navigate to the [AzurePortal](https://portal.azure.com/#create/Microsoft.BingSearch) and create a new resource. After creation, you’ll be redirected to the resource overview page. From there, select "manage keys." ![manage keys](https://github.com/user-attachments/assets/dd2a3c67-d6a7-4198-ba54-67a3c8acff6d)
 2. On the key management page, locate Key1 or Key2 and copy your desired key.
-3. Open the Open WebUI Admin Panel, switch to the Settings tab, and then select Web Search.
+3. Open **Settings > Admin > Web Search**.
 4. Enable the Web search option and set the Web Search Engine to bing.
 5. Fill `SearchApi API Key` with the `API key` that you copied in step 2 from [AzurePortal](https://portal.azure.com/#create/Microsoft.BingSearch) dashboard.
 6. Click `Save`.

docs/features/chat-conversations/web-search/providers/exa.md

@@ -53,7 +53,7 @@ First, you need to sign up for an Exa AI account and get an API key.
 Next, you need to configure the Exa AI integration in the Open WebUI admin settings.
 
 1.  **Log in as an Administrator:** Access your Open WebUI instance and log in with an administrator account.
-2.  **Navigate to Web Search Settings:** Go to the **Admin Panel**, then click on **Settings** > **Web Search**.
+2.  **Navigate to Web Search Settings:** Go to **Settings > Admin > Web Search**.
 3.  **Select Exa as the Search Engine:** In the "Web Search Engine" dropdown menu, select **Exa**.
 4.  **Enter Your API Key:** In the **Exa API Key** input field that appears, paste the API key you copied from the Exa AI dashboard.
 5.  **Save Changes:** Scroll down and click the **Save** button to apply the changes.

docs/features/chat-conversations/web-search/providers/jina.md

@@ -54,7 +54,7 @@ Follow these steps to get an API key:
 To enable the Jina web search integration, follow these steps in the Open WebUI admin settings:
 
 1. **Log in as an Administrator:** Access your Open WebUI instance and log in with an administrator account.
-2. **Navigate to Web Search Settings:** Go to the **Admin Panel**, then click on **Settings** > **Web Search**.
+2. **Navigate to Web Search Settings:** Go to **Settings > Admin > Web Search**.
 3. **Select Jina as the Search Engine:** In the "Web Search Engine" dropdown menu, select **Jina**.
 4. **Enter Your API Key:** Paste your Jina API key into the **Jina API Key** input field.
 5. **(Optional) Enter Jina API Base URL:** If you need to use a specific endpoint (e.g., for EU data processing), enter it in the **Jina API Base URL** field. Default is `https://s.jina.ai/`.

docs/features/chat-conversations/web-search/providers/kagi.md

@@ -35,7 +35,7 @@ Having issues with web search? Check out the [Web Search Troubleshooting Guide](
 
 1. Go to [kagi.com/api](https://kagi.com/api) and set up API billing.
 2. Go to [kagi.com/api/keys](https://kagi.com/api/keys) and create an API key. Copy the key.
-3. Open the **Open WebUI Admin Panel** and click **Settings**, then **Web Search**.
+3. Open **Settings > Admin > Web Search**.
 4. Enable **Web search** and set **Web Search Engine** to `kagi`.
 5. Paste your API key into the **Kagi Search API Key** field.
 6. Click **Save**.

docs/features/extensibility/mcp.mdx

@@ -16,7 +16,7 @@ You **MUST** set the `WEBUI_SECRET_KEY` environment variable in your Docker setu
 ## 🚀 Quick start 
 
 1. Open **⚙️ Settings > Admin > Integrations**.
-2. Click **+ (Add Server)**.
+2. Under **External Tool Servers**, click **+ Add Connection**. The Integrations page holds several sections, so make sure it is that one.
 3. Set **Type** to **MCP (Streamable HTTP)**.
 4. Enter your **Server URL** and **Auth** details (OAuth 2.1, if required).
 5. **Save**. If prompted, restart Open WebUI.
@@ -122,7 +122,7 @@ The provider returns the browser to the Open WebUI home page when the flow finis
 Use this when you already have a client ID/client secret from your identity provider.
 
 1. Open **Settings > Admin > Integrations**.
-2. Click **+ (Add Server)**.
+2. Under **External Tool Servers**, click **+ Add Connection**. The Integrations page holds several sections, so make sure it is that one.
 3. Set **Type** to **MCP (Streamable HTTP)**.
 4. Enter your MCP server **URL**.
 5. In **Auth**, select **OAuth 2.1 (Static)**.