@@ -30,9 +30,10 @@ Ask Sim to build workflows, research a topic, create files, query tables, or act
 
 ## Start a chat [#how-it-works]
 
-1. Select **New chat** in the sidebar.
-2. Choose **Build** for the workspace actions described in this section. Where available, **Search** answers questions from connected sources.
-3. Describe the task, its inputs, and the result you want.
+1. Select **New chat** in a workspace, or **Home** in the organization sidebar.
+2. Describe the task, its inputs, and the result you want.
+
+For questions about connected sources, open **Search → Assistant** in the organization view. Use the **Search** tab to browse results. See [Sim Search](/search).
 
 **Plan** helps research needs and develop a solution before implementation. It appears only for eligible platform administrators with **Super admin mode** enabled on a deployment that enables this capability. An organization Admin role alone does not enable it.
 
@@ -43,7 +44,7 @@ For example:
 - "Create a workflow that takes a contract PDF, extracts key terms, and emails a summary to legal."
 - "Add a daily schedule to the prospect workflow and deploy it. At 8am America/New_York, find new high-fit prospects and post them to #outbound in Slack."
 
-Chat can work across accessible resources. When you open Sim inside a workflow, that conversation is scoped to the workflow. In the organization view, **Build** requires permission to create organization workspaces; each action in an existing workspace still checks its access and enabled capabilities. Available actions depend on your role, connected accounts, workspace settings, and organization policy. Planning a solution does not by itself authorize deploying it or sending messages.
+Chat can work across accessible resources. When you open Sim inside a workflow, that conversation is scoped to the workflow. In the organization view, **Home** requires permission to create organization workspaces; each action in an existing workspace still checks its access and enabled capabilities. Available actions depend on your role, connected accounts, workspace settings, and organization policy. Planning a solution does not by itself authorize deploying it or sending messages.
 
 ## Add context [#adding-context]
 
 
@@ -39,10 +39,12 @@ You do not choose repositories, channels, labels, or an indexing method during p
 | Confluence service account | Connect Confluence. Both your account and the service connection must read the selected content. |
 | Coda | Connect personal Coda MCP. Service mode also verifies the parent document with its REST token. |
 | GitLab | No personal connection. Your verified Sim email must match current GitLab identity and permissions, or the admin's CSV mapping and project grant. |
-| [Generic Secrets, Member mode](/search/generic-secrets) | Select **Manage secrets** in Integrations and save your own values for Build and Plan. |
+| [Generic Secrets, Member mode](/search/generic-secrets) | Select **Manage secrets** in Integrations and save your own values for organization Home conversations. |
 
 Gmail, Calendar, and Drive have separate grants. Connecting one does not authorize the others. Except for GitLab's permission model, a service account restricts resources rather than replacing your personal connection.
 
+Creating Jira sprints requires the Jira sprint permission. If your account was connected before sprint actions were added, reconnect it to grant that permission. Existing Jira operations continue to use their existing permissions.
+
 ## Tool permissions
 
 When Assistant integration actions are enabled, open **Integrations** and select **Tool permissions** beside your connected account. Set a preference for each operation or use the **Read-only tools** and **Write tools** group controls:
@@ -88,5 +90,3 @@ Live Search calls the provider for each request. Waiting for a Sim sync or retry
 
 - [Search access and freshness](/search#access-and-freshness)
 - [Knowledge-base connectors](/knowledgebase/connectors)
-
-Creating Jira sprints requires the Jira sprint permission. If your account was connected before sprint actions were added, reconnect it to grant that permission. Existing Jira operations continue to use their existing permissions.
@@ -18,10 +18,10 @@ Your organization must enable Search and make a source available to you. [Connec
 Read the title and excerpt to find the relevant result. Each result shows its source, with an author and date when available. Select the title to open the original.
 
 <Image
-  src="/static/search/atlas-document-results.webp"
-  alt="Search results for the Atlas onboarding checklist in Confluence, with the organization sidebar and document excerpts"
-  width={2660}
-  height={900}
+  src="/static/search/organization-search.png"
+  alt="Organization Search with the Search and Assistant tabs above the search field"
+  width={1440}
+  height={1000}
   variant="overview"
   background="san-francisco"
 />
@@ -54,10 +54,10 @@ If a query is too broad, add a detail you know: try `product requirements templa
 
 Open the **…** menu beside a result:
 
-- **Summarize** starts a Search conversation about that document. Ask a follow-up to explore it further.
+- **Summarize** opens **Search → Assistant** with that document. Ask a follow-up to explore it further.
 - **Copy link** copies the original source link. Anyone you send it to still needs access in that app.
 
-For an answer that combines several documents, [ask a question in Search](/search/ask-questions).
+For an answer that combines several documents, [ask a question in Assistant](/search/ask-questions).
 
 ## Return to something you found
 
 
@@ -1,30 +1,30 @@
 ---
 title: Generic Secrets
-description: Store shared or personal secrets for Build and Plan
+description: Store shared or personal secrets for organization Home conversations
 ---
 
-Generic Secrets stores values that Build and Plan can use in code and requests. It uses the same [secrets editor as workspaces](/platform/credentials) and does not connect an external account or add searchable documents.
+Generic Secrets stores values that Sim can use in code and requests from an organization **Home** conversation, including **Plan** when available. It uses the same [secrets editor as workspaces](/platform/credentials) and does not connect an external account or add searchable documents.
 
 ## Add the source
 
 An organization admin opens **Settings → Sources → Add source → Generic Secrets** and chooses a mode:
 
-| Mode | Manage values | Use in Build and Plan |
+| Mode | Manage values | Use in Home |
 | --- | --- | --- |
-| **Organization** | Admins open **Secrets** from the source in Settings. | Members with Build access use shared values. Members cannot open the editor to view them. |
+| **Organization** | Admins open **Secrets** from the source in Settings. | Members with Home access use shared values. Members cannot open the editor to view them. |
 | **Member** | Each person opens **Integrations → Generic Secrets → Manage secrets**. | Each person uses only their own values in the organization. |
 
 Only the selected mode is active. To change it, select **Configure** on the source.
 
 ## Use a secret
 
 1. Save a name and value in the editor.
-2. Ask Build or Plan to run code that needs that secret.
-3. The mode sees available names and mounts the names needed by `run_code` or `run_function` as environment variables. Code can use them in requests such as `curl` without putting values in the prompt.
+2. Open **Home** in the organization sidebar and ask Sim to run code that needs that secret.
+3. Sim sees available names and mounts the names needed by `run_code` or `run_function` as environment variables. Code can use them in requests such as `curl` without putting values in the prompt.
 
 In an organization conversation targeting a workspace, an organization secret takes precedence over a workspace secret with the same name. Member mode resolves the current member's values and cannot use another member's secrets.
 
-Generic Secrets is available only in **Build** and **Plan**. Search mode, Search MCP, and Sim Search in Slack cannot mount these values. Workspace secrets remain a separate resource.
+**Search**, including **Assistant**, Search MCP, and Sim Search in Slack cannot mount these values. Workspace secrets remain a separate resource.
 
 ## Remove the source
 
 
@@ -9,7 +9,7 @@ Gmail Search finds matching messages in your connected mailbox. **Member account
 
 An admin adds **Gmail** in **Settings → Sources**, chooses **Member accounts**, and saves. Members select **Integrations → Gmail → Connect**, then search for a known message and read it.
 
-Member mode has no admin label, date, category, or mailbox filters. Search does not send or modify messages, though the shared personal connection may request broader workflow scopes.
+Member mode has no admin label, date, category, or mailbox filters. Search and document-read requests do not send or modify messages. When integration actions are enabled, **Search → Assistant** can create drafts or send email using your connected account, subject to tool permissions and organization policy. Writes ask for [review](/search/ask-questions#review-actions) by default.
 
 ## Set up a central service account
 
 
@@ -82,7 +82,7 @@ Availability depends on deployment configuration and organization policy. Google
 | [Slack](/search/slack) | Accessible messages and files through real-time search | Member only |
 | [Zoom](/search/zoom) | Past meetings and available artifacts; requires organization enablement | Member only |
 
-**Generic Secrets** is also offered in Sources. Its **Organization** and **Member** modes store secrets for Build and Plan; they do not add searchable content. See [Generic Secrets](/search/generic-secrets).
+**Generic Secrets** is also offered in Sources. Its **Organization** and **Member** modes store secrets for organization Home conversations; they do not add searchable content. See [Generic Secrets](/search/generic-secrets).
 
 ## Access and freshness
 
 
@@ -19,7 +19,7 @@ Sim resolves your accessible Atlassian sites and sends Jira Query Language (JQL)
 
 Search returns summaries and descriptions. Reads fetch the issue and available comments with the same account. Jira enforces project permissions, issue security, and app-access restrictions. Bounded responses may omit comments; open Jira for the full discussion.
 
-Search checks up to four accessible sites by default. A native query can select a cloud site ID and follow its continuation cursor. Changes follow Jira's search freshness. Live Search does not crawl attachments or retain an indexed issue copy, and does not edit issues. The shared account connection can request broader workflow permissions.
+Search checks up to four accessible sites by default. A native query can select a cloud site ID and follow its continuation cursor. Changes follow Jira's search freshness. Live Search does not crawl attachments or retain an indexed issue copy. Search and document-read requests do not edit issues. When integration actions are enabled, **Search → Assistant** can create or update issues, add comments, and create sprints using your connected account, subject to tool permissions and organization policy. These writes ask for [review](/search/ask-questions#review-actions) by default.
 
 ## Troubleshooting
 
@@ -40,7 +40,7 @@ Follow [Atlassian OAuth setup](/platform/self-hosting/integrations-oauth#atlassi
 https://<your-sim-domain>/api/auth/oauth2/callback/jira
 ```
 
-Search reads only, but the shared app also supports workflows. If only the app owner can connect, check **Distribution**. After client/scope changes, update the organization's saved provider configuration and reconnect affected members.
+The shared app supports Search retrieval, supported Assistant actions, and workflows. If only the app owner can connect, check **Distribution**. After client/scope changes, update the organization's saved provider configuration and reconnect affected members.
 
 ## Related docs
 
 
@@ -7,7 +7,7 @@ description: What to check when sources, results, or answers aren't what you exp
 
 Check that you're in the intended organization. Ask your admin whether Search is enabled for your organization and account.
 
-A missing conversation-mode menu on **Home** is expected for members without builder access: Home starts in Search automatically, so you can ask immediately. If the menu is shown, choose **Search** before sending your first message.
+Open **Search** in the organization sidebar, then select **Assistant** to ask a question. Access to Search does not require permission to create organization workspaces.
 
 ## I can't connect an app
 
@@ -52,9 +52,9 @@ For a multi-part question, ask for one part first. If an answer has no source, a
 
 Open the original source and compare it with the answer. Specify the relevant dates, and ask Sim to distinguish final decisions from earlier proposals. If documents disagree, ask it to explain the conflict with citations rather than combine them into one answer.
 
-## I can't attach a PDF or spreadsheet in Search mode
+## I can't attach a PDF or spreadsheet in Assistant [#i-cant-attach-a-pdf-or-spreadsheet-in-search-mode]
 
-Search conversations accept image attachments. Find document content through a connected source, use **Summarize** on its search result, or paste a relevant excerpt into your question. Don't assume that other Sim modes' upload capabilities apply to Search.
+Assistant accepts image attachments. Find document content through a connected source, use **Summarize** on its search result, or paste a relevant excerpt into your question. Other Chat surfaces support different upload types.
 
 ## A colleague sees different results
 
 
@@ -17,7 +17,7 @@ A workflow Zoom connection does not authorize Search. Its dedicated app registra
 
 ## Search and read meetings
 
-Ask Sim on **Home**: “Search Zoom for deployment rollback decisions last week and cite the transcript.” Use short plain keywords such as `deployment rollback`. Zoom matches topics, agendas, and available meeting content.
+Open **Search → Assistant** and ask Sim: “Search Zoom for deployment rollback decisions last week and cite the transcript.” Use short plain keywords such as `deployment rollback`. Zoom matches topics, agendas, and available meeting content.
 
 Results identify past occurrences by UUID rather than recurring meeting number. Use native kind `meeting` when sending multiple queries to one account. `startDate` and `endDate` use actual start time, with an exclusive end. Continue `nextCursor` with the same account, query, and filters; rerun an expired continuation. [Zoom's Meetings API](https://developers.zoom.us/docs/api/meetings/) documents a 15-minute page-token lifetime; restart Search if the MCP continuation expires.