Name which Integrations page to use, warn about the image model in the chat selector, and correct the folder menu

The settings sidebar now lists Personal and Admin sections together, and Integrations appears in both, once under Services and once under Tools. The Open Terminal connection guide said Settings then Integrations, which no longer identifies one of them, and a reader who picks the personal entry configures a connection for their own account and gets a deployment that does not behave as the guide describes. Both mentions now say which section they mean and what the personal one does instead.

Image generation gains a warning about the setup mistake people actually make. The model selector stays on a normal chat model, since the image model is configured once in the admin settings and never chosen there. Selecting the image model to chat with leaves everything looking configured while generation fails, so the warning names it as the first thing to check.

The folder documentation described a right-click menu for moving conversations. Right-clicking gives you the browser's own menu. The action lives in the three-dot menu that appears when hovering a conversation, and the entry is Move rather than Move to Folder. The two folder-level instructions had the same error.

Author: Classic298

docs/features/chat-conversations/chat-features/conversation-organization.md

@@ -30,15 +30,15 @@ Create a new folder to organize your conversations:
 Organize existing chats by moving them into folders:
 
 - **Drag and Drop**: Click and drag any conversation from the sidebar into a folder.
-- **Right-click Menu**: Right-click on a conversation and select "Move to Folder".
+- **Conversation menu**: Hover a conversation in the sidebar, click the three-dot menu that appears, then choose **Move** and pick the folder.
 
 ### Nested Folders
 
 Folders can be nested within other folders to create hierarchical organization:
 
-- **Create subfolder from menu**: Right-click (or click the three-dot menu ⋯) on any folder and select **"Create Folder"** to create a new subfolder directly inside it.
+- **Create subfolder from menu**: Click the three-dot menu on any folder and select **"Create Folder"** to create a new subfolder directly inside it.
 - **Drag and drop**: Drag a folder onto another folder to make it a subfolder.
-- **Move via context menu**: Right-click on a folder and use the move option to relocate it under a different parent.
+- **Move via folder menu**: Open the same three-dot menu on a folder and use the move option to relocate it under a different parent.
 - Folders can be expanded or collapsed to show/hide their contents.
 - Subfolder names must be unique within the same parent folder. If a duplicate name is entered, a number is automatically appended (e.g., "Notes 1").
 

docs/features/chat-conversations/image-generation-and-editing/usage.md

@@ -20,6 +20,12 @@ If **Image** is missing from the **Integrations** menu entirely, then either ima
 
 ![Image Generation Tutorial](/images/tutorial_image_generation_2.png)
 
+:::warning Keep chatting with your chat model
+The model selector at the top of the chat stays on your normal chat model. The image model is configured once in the admin image settings and is never selected there.
+
+Picking the image model as the chat model is the most common setup mistake. Everything looks configured, and generation fails or returns nothing useful, because an image model cannot hold a conversation and is not being asked for a picture in the way it expects. If image generation has stopped working and the settings look right, check what the model selector says first.
+:::
+
 What happens next depends on the **Function Calling** mode. It can be set per chat in **Chat Controls** > **Advanced Params**, for yourself in **Settings** > **General** > **Advanced Parameters**, per model in the model editor or globally under **Model Defaults** in the admin model settings. The first of those that is not **Default** wins, and Native applies when none of them is set.
 
 **Native** takes the tool path described below. In **Legacy** mode every message you send while the toggle is on goes straight to the image engine, whatever you asked for. It edits instead of creating when the recent conversation carries images and **Image Edit** is on. On the create path a task model rewrites your message into the image prompt first, unless you switch **Image Prompt Generation** off in the admin settings.

docs/features/open-terminal/setup/connecting.md

@@ -25,6 +25,8 @@ Click your **name** at the bottom of the left sidebar to open the user menu, the
 
 In the Admin Panel, click **Settings** in the top nav, then click **Integrations**.
 
+The settings sidebar lists **Integrations** twice, once under **Personal** in the *Services* group and once under **Admin** in the *Tools* group. Open Terminal belongs in the Admin one. Configuring the personal entry connects the terminal to your account alone and the deployment will not work as described here.
+
 ![Admin Panel, Settings → Integrations](/images/open-terminal-integrations-page.png)
 
 ### 3. Find the "Open Terminal" section
@@ -109,7 +111,7 @@ For Docker deployments, you can configure terminal connections automatically usi
 Adding a terminal connection via personal Settings sends the API key to your browser and routes requests directly from it. This is fine for **quick testing**, but for anything beyond that, use Admin Settings instead. It's more secure and works for all users automatically.
 :::
 
-If you need to test a connection without admin access, you can add one from **Settings → Integrations → Open Terminal**. The same URL and API key fields apply.
+If you need to test a connection without admin access, you can add one from the **Personal** part of settings, under *Services*, at **Integrations → Open Terminal**. The same URL and API key fields apply, and the connection is yours alone rather than the instance's.
 
 ---