[Docs] Correct recent user-facing guidance

apps/docs/automations.mdx

@@ -69,11 +69,12 @@ automation reports and structured follow-ups in one review queue. Open
 **Results** from the main navigation to see unread items ordered by priority and
 recency. Critical and high-priority findings appear before normal results.
 
-Use **Check** to open a result and review its full report and suggested work.
-From there, you can edit the prepared prompt, choose a model, and start it as a
-normal session. The item is marked accepted only after the session starts. Use
-**Clear** when no follow-up is needed, or **Clear all** to dismiss the current
-queue.
+Select a result to read its full report. Reports link to the source task or
+session and, when available, its pull request, plan, or artifact. Suggested work
+offers **Start investigation**, where you can edit the prepared prompt and
+choose a model before starting a normal session. The item is accepted only
+after that session starts. Use **Clear** when no follow-up is needed, or **Clear
+all** to dismiss the current queue.
 
 The inbox complements configured chat and Email report destinations rather
 than replacing them. Automation runs still keep their normal sessions and

apps/docs/fast-sessions.mdx

@@ -42,7 +42,7 @@ search them live by name or description. An additional checkout does not
 provision another environment's services.
 
 You can name a repository loosely ("my fork of widgets", "the billing repo")
-without setting up an environment for it. Fast sees the deployment's active
+without setting up an environment for it. Roomote sees the deployment's active
 connected repositories and can search all of them by name or description, so it
 resolves the repository itself and asks only when several plausibly match.
 
@@ -123,7 +123,11 @@ requirements, pagination limits, and the code-search deprecation.
 ## The session view
 
 A session header shows the other people currently viewing that session. Your
-own avatar is omitted from the viewer list.
+own avatar is omitted from the viewer list. If you can manage the session,
+select its title to rename it. The **More actions** menu can stop every active
+task in the session without deleting its work, or archive the session and its
+attached tasks. Archiving is reversible, keeps artifacts and memories, and
+cancels the session's scheduled wakeups.
 
 A session timeline shows prompts, replies, and delegated execution activity.
 Execution cards show their status, workspace, pull requests, artifacts, latest

apps/docs/integrations/index.mdx

@@ -62,12 +62,35 @@ silently bypassed with another connection method.
 ## Manage available tools
 
 Some connected integrations expose a **Manage tools** action in
-**Settings > Integrations**. Admins can use it to restrict the types of
-operations Roomote can make with the service.
-
-Use this as a coarse permissions system, for example allowing only read
-operations or restricting access to a certain type of entity. The list varies
-depending on the integration.
+**Settings > Integrations**. The dialog groups tools into read-only and
+write/delete sections when the integration supplies that metadata. Clear a
+tool's checkbox to hide it from agents and block direct calls to it at the
+Roomote proxy.
+
+Admins can also enable **Integration tool approvals** under **Settings >
+Experimental**. Each tool then has one of four approval modes:
+
+- **Always allow** keeps the normal behavior.
+- **Ask first** pauses each call for the session owner.
+- **Auto (preview)** still asks first, but records what the configured decision
+  model would have recommended so you can compare it with the owner's choice.
+  The model never decides the call while this mode is a preview.
+- **Reject** blocks the tool outright.
+
+An approval card shows the integration and tool, with sanitized arguments under
+**Details**. The owner can **Allow once**, **Allow for this session**, or
+**Deny**. The session-wide choice applies only to later calls to that tool in
+the same session; it does not change the saved policy. Unanswered requests
+expire and fail closed. A delegated task asks its parent session's owner, while
+an unattended task with nobody who can answer cannot run an **Ask first** tool.
+
+Deployment policies are managed by admins and apply from the next session turn.
+Members can set personal policies from a personal integration or MCP server's
+**Manage tools** dialog for their own sessions. Where both deployment and
+personal policies govern a built-in integration, the stricter one wins; a
+personal policy cannot loosen an admin's restriction. Session owners can also
+request an **Ask first** override for an otherwise allowed tool from its
+transcript call.
 
 Some integrations can only list tools after the first user links their account
 from [Personal Settings](/personal-settings).

apps/docs/memory.mdx

@@ -270,6 +270,10 @@ trivial task work keeps the plain completion line unless it came with a
 correction, and [private sessions](/private-sessions) and private tasks are
 never checked.
 
+When this automatic check saves one or more memories, the session or task
+transcript shows an expandable **Saved to memory** entry with the redacted facts
+that were recorded.
+
 Additional memory integrations, such as Supermemory, can also provide shared
 context to tasks and sessions. Roomote chooses one connected memory
 store for the initial recall so multiple stores do not repeat the same preflight.

apps/docs/providers/inference/xai-subscription.mdx

@@ -15,7 +15,7 @@ authorization flow with the account that owns the eligible plan. No API key or
 deployment environment variable is required.
 
 Subscription models keep the `xai/` prefix. Connecting the subscription seeds
-**Grok 4.6** as the default coding model. Grok chat models that xAI publishes
+**Grok 4.7** as the default coding model. Grok chat models that xAI publishes
 after the connection appear in **Settings > Models** and the task model
 switcher automatically, without a Roomote update; image and video Grok models
 are omitted, and models you disable or remove stay that way. When both

apps/docs/providers/inference/xai.mdx

@@ -22,7 +22,7 @@ XAI_API_KEY=...
 ```
 
 Roomote exposes Grok models with the `xai/` prefix. Connecting xAI seeds
-**Grok 4.6** as the default coding model, and Grok chat models released after
+**Grok 4.7** as the default coding model, and Grok chat models released after
 the connection appear automatically, without a Roomote update. Models you
 disable or remove stay that way. Deployments configured only through the
 `XAI_API_KEY` environment variable start picking up new models once model