fix(search): verify setup recovery and refresh guides

Author: waleedlatif1

apps/docs/content/docs/search/confluence.mdx

@@ -63,8 +63,8 @@ Keep **Content Type** at its default for pages, or choose blog posts or both. Le
 <Image
   src="/static/search/confluence-setup.jpg"
   alt="Confluence Search source configuration showing connection method, account, domain, and spaces"
-  width={1280}
-  height={720}
+  width={1470}
+  height={1277}
 />
 
 </Step>
@@ -164,7 +164,7 @@ Existing organization members see the configured Confluence source and their own
 
 With a central account, Sim applies space access together with the page's restrictions and inherited ancestor restrictions. Group membership is refreshed in the background. With member accounts, each person's provider listing determines the pages available to them. A Sim organization admin does not automatically receive access to every Confluence document.
 
-New content and permission changes require a sync and processing before Search reflects them. Open **Manage** on the source to inspect errors, edit its configuration, or trigger a sync. If your own account needs authorization again, use **Reconnect** on the source row.
+New content and permission changes require a sync and processing before Search reflects them. Open the source under **Settings → Integrations → Providers** to inspect errors, edit its configuration, or trigger a sync. If your own account needs authorization again, use **Reconnect** on the source row.
 
 ## Troubleshooting
 

apps/docs/content/docs/search/connect-your-account.mdx

@@ -23,9 +23,8 @@ Accept your Sim organization invitation or sign in through your organization's S
 
 Open **Integrations**, find the provider or source, and select **Connect account**. Your first connection may ask for required source settings, such as repository or project names. If the provider is missing, ask an organization admin to approve it.
 
-<Image src="/static/search/connect-account.png" alt="Google Drive source row with Connect account" width={1280} height={720} />
+<Image src="/static/search/connect-account.png" alt="Organization Integrations with an approved Gmail provider and Connect account action" width={1470} height={1277} />
 
-*Workspace Search is shown here. Organization sources are managed in Settings → Integrations.*
 
 </Step>
 <Step>
@@ -67,7 +66,7 @@ Connecting one Google service does not connect all of them. Gmail, Calendar, and
 | **Reconnect** | Authorize the same source account again. |
 | **Finish connecting in the other tab** | Finish authorization, or use **Open again**. Allow popups for Sim. |
 | No results | Check the source's filters and sync status with your admin. Confirm you can open the document at the source. |
-| Needs admin attention | Ask your admin to inspect **Manage** for the source error. |
+| Needs admin attention | Ask your admin to open the source in **Settings → Integrations → Providers** to inspect its error. |
 
 <Callout type="info">
   Your Sim role does not override document access at the source. Connecting a different account or receiving a Search link does not share someone else's mailbox, private calendar, or restricted documents with you.

apps/docs/content/docs/search/github.mdx

@@ -111,6 +111,8 @@ As a Sim organization admin, open **Settings → Integrations → Providers**, a
 
 Enter the repository and keep **Sync documents with → Connected members** for the usual setup.
 
+<Image src="/static/search/github-setup.jpg" alt="GitHub source configuration with account, repository, branch, and path fields" width={1470} height={1277} />
+
 | Field | What to enter |
 |---|---|
 | Repository | `owner/repo`. Add another source for another repository. |
@@ -129,7 +131,7 @@ You can instead select an existing account under **Sync documents with** to supp
 
 On the GitHub source row, select **Connect account** and authorize the App. Teammates repeat this step after joining the Sim organization. For private repositories, both the person's account and the App installation must have access. GitHub also permits App user tokens to read public repositories without an installation; see [GitHub's permission rules](https://docs.github.com/en/apps/creating-github-apps/registering-a-github-app/choosing-permissions-for-a-github-app).
 
-With **Connected members**, indexing begins after someone connects. A dedicated indexing account can start syncing immediately; each teammate still connects before searching. Admins can open **Manage** on the source to inspect sync progress and errors.
+With **Connected members**, indexing begins after someone connects. A dedicated indexing account can start syncing immediately; each teammate still connects before searching. Admins can open the source under **Settings → Integrations → Providers** to inspect sync progress and errors.
 
 </Step>
 </Steps>

apps/docs/content/docs/search/gitlab.mdx

@@ -9,7 +9,7 @@ import { Image } from '@/components/ui/image'
 
 GitLab Search uses an administrator connection to sync a project's content and permissions. Teammates do not connect individual GitLab accounts. They sign in to the Sim organization with a verified email matching their confirmed GitLab email.
 
-<Image src="/static/search/gitlab-setup.jpg" alt="GitLab source setup in Sim Search" width={1280} height={720} />
+<Image src="/static/search/gitlab-setup.jpg" alt="GitLab source setup in Sim Search" width={1470} height={1277} />
 
 Admin setup uses your organization's **Settings → Integrations** page. Teammates do not need a personal GitLab connection. For workspace Search, use **Search → Add source** instead.
 
@@ -61,7 +61,7 @@ Open **Settings → Integrations → Providers**, approve **GitLab**, then selec
 | Issue State / Labels / Milestone | Optional filters for issues. |
 | Max Items | Optional positive limit. Leave blank for all matching items. |
 
-<Image src="/static/search/gitlab-options.jpg" alt="GitLab source configuration scrolled to repository and issue filters, item limit, and document details" width={1280} height={720} />
+<Image src="/static/search/gitlab-options.jpg" alt="GitLab source configuration scrolled to repository and issue filters, item limit, and document details" width={1470} height={1277} />
 
 Select **Connect & Sync**. Sim validates the token and source policy, then starts indexing.
 
@@ -72,7 +72,7 @@ Select **Connect & Sync**. Sim validates the token and source policy, then start
 
 Invite teammates to the Sim organization using their verified work email. Sim matches that email against the GitLab directory and applies project, feature, and confidential-issue permissions. No GitLab **Connect account** step is required.
 
-Admins can open **Manage** on the source to review sync progress. Permission and membership changes are picked up during background refreshes.
+Admins can open the source under **Settings → Integrations → Providers** to review sync progress. Permission and membership changes are picked up during background refreshes.
 
 </Step>
 </Steps>

apps/docs/content/docs/search/gmail.mdx

@@ -39,7 +39,7 @@ Click **Add source**. Gmail appears in the **Sources** list. Each person, includ
 </Step>
 </Steps>
 
-<Image src="/static/search/gmail-setup.jpg" alt="Gmail Search source configuration" width={1280} height={720} />
+<Image src="/static/search/gmail-setup.jpg" alt="Gmail Search source configuration" width={1470} height={1277} />
 
 ## Connect your account
 
@@ -51,7 +51,7 @@ Teammates follow these same steps after joining the organization. Once an admin
 
 ## Source options
 
-An admin can change these under **Manage** on the Gmail source. Filters apply separately to each connected mailbox.
+An admin can change these in the Gmail source's **Settings** tab. Filters apply separately to each connected mailbox.
 
 | Option | Behavior |
 | --- | --- |

apps/docs/content/docs/search/google-calendar.mdx

@@ -41,7 +41,7 @@ Keep the default date range for the previous and next 30 days, then click **Add
 </Step>
 </Steps>
 
-<Image src="/static/search/google-calendar-setup.jpg" alt="Google Calendar Search source configuration" width={1280} height={720} />
+<Image src="/static/search/google-calendar-setup.jpg" alt="Google Calendar Search source configuration" width={1470} height={1277} />
 
 <Callout type="info">
   `primary` means the connected person's main calendar. A calendar selected from the list is a specific calendar ID, even when it is your main calendar. That same ID applies to every member, and only members with access to it can search its events.
@@ -57,7 +57,7 @@ Teammates repeat only these connection steps after joining the organization. The
 
 ## Source options
 
-An admin can change these under **Manage** on the source.
+An admin can change these in the source's **Settings** tab.
 
 | Option | Behavior |
 | --- | --- |

apps/docs/content/docs/search/google-drive.mdx

@@ -54,7 +54,7 @@ Select **Add source**, then **Connect account** on the source row. Use the Googl
 
 This requires a Google Workspace domain and a Workspace super administrator to authorize domain-wide delegation. Consumer Gmail accounts cannot use this path.
 
-<Image src="/static/search/google-drive-setup.jpg" alt="Google Drive Search service-account connection and source options" width={1280} height={720} />
+<Image src="/static/search/google-drive-setup.jpg" alt="Google Drive service-account setup with Crawl as and manual folder fields" width={1470} height={1277} />
 
 <Steps>
 <Step>
@@ -95,7 +95,7 @@ These are Search's central crawl scopes. The general [Google service account gui
 
 In Google Drive's Search setup, choose **Service account**. Open the **Service account** picker, choose its connection action, and paste the JSON key into **Add Google Service Account**. Give it a name and add it. Sim returns you to the source form with that credential selected.
 
-<Image src="/static/search/google-service-account.jpg" alt="Add Google Service Account credential modal in Sim" width={1280} height={720} />
+<Image src="/static/search/google-service-account.jpg" alt="Add Google Service Account credential modal in Sim" width={1470} height={1277} />
 
 </Step>
 <Step>
@@ -119,14 +119,14 @@ Set **Crawl as** to a Google Workspace administrator who can read groups, member
 
 Sim exports Docs and Slides as text and Sheets as XLSX spreadsheets. Supported uploaded files use the knowledge-base document pipeline, including PDF and Office formats. Unsupported files and oversized exports cannot be indexed; Google limits Workspace exports to 10 MB. See [Drive export formats](https://developers.google.com/workspace/drive/api/guides/ref-export-formats) and [download limits](https://developers.google.com/workspace/drive/api/guides/manage-downloads).
 
-Search schedules syncs hourly. Content, deletions, and permissions refresh in the background; results are not a live read from Drive. Admins can inspect progress and errors through **Manage** on the source.
+Search schedules syncs hourly. Content, deletions, and permissions refresh in the background; results are not a live read from Drive. Admins can inspect progress and errors by opening the source under **Settings → Integrations → Providers**.
 
 ## Troubleshooting
 
 | Problem | Next step |
 | --- | --- |
 | Directory access failed | Check the delegated scopes and the **Crawl as** user's administrator privileges. A normal Google OAuth credential cannot supply this central Search path. |
-| An existing central source uses a normal Google OAuth account | Replace it with a delegated service account. If the source is **Disabled**, choose **Resume** first. Then open **Manage**, select or add the delegated service account, and choose **Change indexing account**. A **Paused** source can change credentials before you resume it. |
+| An existing central source uses a normal Google OAuth account | Open the source's **Settings** tab, select or add a delegated service account, and choose **Change indexing account**. If the source is **Paused** or **Disabled**, choose **Resume** after updating the account. |
 | Missing files in a central crawl | Open them as the **Crawl as** user. Delegation does not grant that user access to all domain files. Check folder and file-type filters. |
 | A teammate sees no results | Confirm their verified Sim email matches the Drive permission or group membership. For member accounts, finish their personal Drive connection too. |
 | A public or shared-link file is missing | Check **Openly shared files**. Link-only sharing does not grant Search access. A named user or group permission can still make the file searchable. |

apps/docs/content/docs/search/index.mdx

@@ -39,9 +39,8 @@ In **Integrations**, select **Connect account** if prompted—even if you create
 </Step>
 </Steps>
 
-<Image src="/static/search/add-source.jpg" alt="Sim Search source catalog with Set up actions" width={1280} height={720} />
+<Image src="/static/search/add-source.jpg" alt="Sim Search source catalog with Set up actions" width={1470} height={1277} />
 
-*Workspace Search is shown here. Organization sources are managed in Settings → Integrations.*
 
 Source availability depends on the deployment and organization policy. An unavailable source needs operator configuration before setup can continue.
 
@@ -78,7 +77,7 @@ Some member sources offer **Sync documents with**. **Connected members** uses me
 
 Invite people through the organization's **Settings → Members**, or use your organization's [SSO provisioning](/platform/enterprise/sso). Share the organization's **Home** or **Integrations** URL. People need their own Sim account and organization membership; they do not need access to a workspace. Connecting an external account alone does not grant organization membership.
 
-Organization admins manage source configuration and sync status through **Manage** under **Settings → Integrations → Providers**. Other members connect or reconnect their own accounts. See [Connect your account](/search/connect-your-account) for the teammate walkthrough.
+Organization admins manage source configuration and sync status by opening a source under **Settings → Integrations → Providers**. Other members connect or reconnect their own accounts. See [Connect your account](/search/connect-your-account) for the teammate walkthrough.
 
 ## Search, Assistant, and MCP
 
@@ -103,7 +102,9 @@ Search runs background syncs on an hourly schedule. Large sources, provider limi
 
 A completed sync means the source was checked; some documents may still be indexing. The source row shows how many documents you can search and whether indexing failed for any documents you can access.
 
-As an admin, open **Manage → Documents** and select **Failed** from the status dropdown to inspect those files. Use the search field to find a document by name. **Settings** contains the source configuration and **Sync history** shows recent runs. Select **Retry indexing** beside a file to try again. **Exclude** removes a file from search; select **Excluded** and then **Restore** to include it again. Fix a disconnected account or source configuration before retrying a sync that needs attention.
+As an admin, open the source under **Settings → Integrations → Providers**. In **Documents**, select **Failed** from the status dropdown to inspect those files. Use the search field to find a document by name. **Settings** contains the source configuration and **Sync history** shows recent runs. Select **Retry indexing** beside a file to try again. **Exclude** removes a file from search; select **Excluded** and then **Restore** to include it again. Fix a disconnected account or source configuration before retrying a sync that needs attention.
+
+<Image src="/static/search/source-documents.jpg" alt="Source document page with search, status filtering, indexing recovery, and header actions" width={1470} height={1277} />
 
 Temporary indexing-capacity waits retry automatically in the background. If automatic retries are exhausted, the document appears as failed so an admin can retry it. Other searchable documents remain available while this work finishes.
 

apps/docs/content/docs/search/jira.mdx

@@ -47,9 +47,9 @@ If you already know the project keys, use the switch beside **Projects** to sele
 
 <Image
   src="/static/search/jira-setup.jpg"
-  alt="Jira Search source setup with member accounts, an example site, and a project key"
-  width={1280}
-  height={720}
+  alt="Jira Search source setup with member accounts and required site and project fields"
+  width={1470}
+  height={1277}
 />
 
 </Step>
@@ -88,7 +88,7 @@ Search manages the sync schedule. Item limits and sync frequency are not setup d
 
 Existing organization members see the same source configuration and their own **Connect account**, **Reconnect**, or indexing status. They do not choose projects again. Invite new teammates to the Sim organization through its Members settings or SSO onboarding, then have them open Integrations and connect Jira. A Jira authorization does not grant Sim organization membership.
 
-Sim checks Jira separately using each connected person's account. Issue content and tags become searchable as processing finishes; changes and lost issue access are picked up by later syncs. The source row reports the number of documents searchable by the current viewer. Admins can open **Manage** to review sync status or update the source.
+Sim checks Jira separately using each connected person's account. Issue content and tags become searchable as processing finishes; changes and lost issue access are picked up by later syncs. The source row reports the number of documents searchable by the current viewer. Admins can open the source under **Settings → Integrations → Providers** to review sync status or update the source.
 
 ## Troubleshooting
 

apps/docs/content/docs/search/slack.mdx

@@ -8,7 +8,7 @@ import { Image } from '@/components/ui/image'
 
 Slack Search indexes channel messages and threads. A Sim organization admin configures your Slack app once, then each teammate authorizes their own Slack account. Their results are limited to the selected public channels and private channels they can access. DMs and group DMs are not indexed.
 
-<Image src="/static/search/slack-setup.jpg" alt="Slack source setup in Sim Search" width={1280} height={720} />
+<Image src="/static/search/slack-setup.jpg" alt="Slack app setup for Sim Search with application and client credential fields" width={1470} height={1277} />
 
 ## Before you start
 
@@ -76,7 +76,7 @@ Select **Add source**. On the source row, each person selects **Connect account*
 
 You can instead select an existing account under **Sync documents with** to supply message content centrally. Members still connect their own accounts to establish access. The selected account must itself be able to read the selected channels.
 
-Admins can use **Manage** to inspect sync progress. Search reads the indexed content, so source changes appear after background syncing. Slack retention and API limits determine how much history is available.
+Admins can open the source under **Settings → Integrations → Providers** to inspect sync progress. Search reads the indexed content, so source changes appear after background syncing. Slack retention and API limits determine how much history is available.
 
 ## Permissions reference