公司員工可透過 Google Cloud Search，從公司內部資料存放區搜尋及擷取資訊，例如內部文件、資料庫欄位和 CRM 資料。
架構總覽
圖 1 顯示 Google Cloud Search 實作的所有重要元件：
圖 1. Google Cloud Search 的主要元件
圖 1 中最重要的詞彙定義如下：
存放區
企業用來儲存資料的軟體，例如用來儲存員工資訊的資料庫。
資料來源
已編列索引並儲存在 Google Cloud Search 中的存放區資料。
搜尋介面
員工用來搜尋資料來源的使用者介面。您可以開發搜尋介面，在任何裝置上使用，從手機到桌機都沒問題。您也可以部署 Google 提供的搜尋小工具，在內部網站中啟用搜尋功能。每次搜尋都會附上搜尋應用程式 ID，確保系統瞭解搜尋情境，例如在客戶服務工具中搜尋。cloudsearch.google.com 網站包含搜尋介面。
資料結構：說明企業存放區中的資料應如何呈現，才能供 Google Cloud Search 使用。架構會定義員工的 Google Cloud Search 體驗，例如篩選和顯示內容的方式。
內容連結器
一種軟體程式，用於遍歷企業存放區中的資料，並填入資料來源。
身分識別連接器
這類軟體程式會將企業身分 (使用者和群組) 同步至 Google Cloud Search 要求的身分。
Google Cloud Search 應用實例
以下列舉幾個可透過 Google Cloud Search 解決的應用實例：
員工需要尋找公司政策、文件和其他員工撰寫的內容。
客服團隊成員需要找出相關的疑難排解文件，並傳送給顧客。
員工需要尋找公司專案的內部資訊。
銷售代表想查看特定客戶的所有支援問題狀態。
員工想瞭解公司專用術語的定義。
導入 Google Cloud Search 的第一步，是找出 Google Cloud Search 解決的用途。
導入 Google Cloud Search
根據預設，Google Cloud Search 會為 Google 文件和試算表等 Google Workspace 資料建立索引。您不需要為 Google Workspace 資料導入 Google Cloud Search。不過，您必須為非 Google Workspace 資料 (例如儲存在第三方資料庫、Windows Fileshare 等檔案系統、OneDrive 或 SharePoint 等內部網路入口網站的資料) 導入 Google Cloud Search。如要為企業導入 Google Cloud Search，請按照下列步驟操作。
[null,null,["上次更新時間：2025-08-29 (世界標準時間)。"],[],[],null,["# Introduction to Google Cloud Search\n\nGoogle Cloud Search allows employees of a company to search and retrieve\ninformation, such as internal documents, database fields, and CRM data,\nfrom the company's internal data repositories.\n| **Warning:** You must sign up for a Google Cloud Search account before you can use the APIs and SDKs. To sign up, visit the [Cloud Search product page](https://workspace.google.com/products/cloud-search/).\n\nArchitectural overview\n----------------------\n\nFigure 1 shows all the key components of a Google Cloud Search implementation:\n**Figure 1.** Key components of Google Cloud Search\n\nHere are the definitions of the most important terms from Figure 1:\n\n*Repository*\n: Software used by an enterprise to store its data, such as\n database used to store employee information.\n\n*Data source*\n: Data from a repository that has been indexed and stored in\n Google Cloud Search.\n\n*Search interface*\n: The user interface used by employees to search\n a data source. A search interface can be developed for use on any device, from a\n mobile phone to a desktop computer. The Google-provided search widget can also be\n deployed to enable search within your internal web sites. The search\n application ID is included with every search to ensure that the context of that\n search, such as within a customer service tool, is known. The site\n cloudsearch.google.com contains a search interface.\n\n*Search application*\n: A group of settings that, when associated with a search\n interface, provide contextual information about searches. Contextual information\n includes the data sources and search rankings that should be used for a search\n using that interface. Search applications also include mechanisms for filtering\n results and enable reporting on data sources, such as number of queries made\n over a given time period.\n\n*Schema*\n: A data structure outlining how the data in a enterprise's\n repository should be represented for Google Cloud Search. A schema defines the\n employee Google Cloud Search experience, such as how things are filtered and\n displayed.\n\n*Content connector*\n: A software program used to traverse the data in an\n enterprise's repository and populate a data source.\n\n*Identity connector*\n: A software program used to sync enterprise identities\n (users and groups) to the identities required by Google Cloud Search.\n\nGoogle Cloud Search use cases\n-----------------------------\n\nHere are some use cases that might be solved by Google Cloud Search:\n\n- Employees need a way to find corporate policies, documents, and content authored by other employees.\n- Customer service team members need to find relevant troubleshooting documents to send to customers.\n- Employees need to find internal information about company projects.\n- A sales representative wants to view the status of all support issues for a particular customer.\n- Employees want a definition for a company-specific term.\n\nThe first step in implementing Google Cloud Search is to identify the use cases\nsolved by Google Cloud Search.\n\nImplement Google Cloud Search\n-----------------------------\n\nBy default, Google Cloud Search indexes Google Workspace data, such as\nGoogle documents and spreadsheets. You do not need to implement Google Cloud Search for Google Workspace data. However, you need to implement Google Cloud Search for non-Google Workspace data, such as data stored in a third-party\ndatabase, file systems like Windows Fileshare, OneDrive or intranet portals\nlike Sharepoint. The following steps are required to implement Google Cloud Search for your enterprise.\n\n1. Determine a use case that Google Cloud Search helps to solve.\n2. Identify the repositories holding data relevant to the use case.\n3. Identify the identity systems used by your company to manage access to data in each repository.\n4. [Configure access to the Google Cloud Search API](/workspace/cloud-search/docs/guides/project-setup).\n5. [Add a data source to Google Cloud Search](https://support.google.com/a/answer/7056471).\n6. [Create and register a schema](/workspace/cloud-search/docs/guides/schema-guide) for each data source.\n7. Determine if there is a content connector available for your repository. For a list of pre-built connectors, refer to the [Cloud Search connector directory](/workspace/cloud-search/docs/connector-directory). If a content connector is available, skip to step 9.\n8. [Create a content connector](/workspace/cloud-search/docs/guides/content-connector) to access data in each repository and index it into a Cloud Search data source.\n9. Determine if you need an [identity connector](/workspace/cloud-search/docs/guides/identity-mapping). If you don't need an identity connector, skip to step 11.\n10. [Create an identity connector](/workspace/cloud-search/docs/guides/identity-connector) to map your repository or enterprise identities to Google identities.\n11. [Set up search applications](https://support.google.com/a/answer/9043922).\n12. [Create a search interface](/workspace/cloud-search/docs/guides/search-interface) to perform search queries.\n13. Deploy your connectors and search interfaces. If you used a pre-built connector, follow the instructions for the connector to obtain and deploy the connector. Available connectors are listed in the [Google Cloud Search Connector Directory](/workspace/cloud-search/docs/connector-directory)\n\nNext steps\n----------\n\nHere are a few next steps you might take:\n\n1. Try the [Google Cloud Search getting started tutorial](/workspace/cloud-search/docs/tutorials/end-to-end).\n2. Determine use case(s) for which you'll use Google Cloud Search.\n3. Identify the repositories relevant to these use cases.\n4. Identify any identity systems used by your repositories.\n5. Continue to [Configure access to the Google Cloud Search API](/workspace/cloud-search/docs/guides/project-setup)."]]
