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 Workspace 数据（例如 Google 文档和电子表格）编入索引。Google Workspace 数据不需要实现 Google Cloud Search。但是，非 Google Workspace 数据（如存储在第三方数据库中的数据）、文件系统（如 Windows Fileshare、OneDrive）或内网门户（如 Sharepoint）则需要实现 Google Cloud Search。要为您的企业实现 Google Cloud Search，您需要按以下步骤操作。
[null,null,["最后更新时间 (UTC)：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)."]]
