Stay organized with collections
Save and categorize content based on your preferences.
By default, Google Cloud Search indexes all of your Google Workspace data.
You can also create your own custom program, called a connector, to index
data stored in a third-party repository. A connector can be a separate program,
a script that runs in its own process, or an add-on to your repository.
There are two types of connectors: content connectors and
identity connectors. Content connectors are used to traverse a repository and
index the data so that Google Cloud Search can effectively search that data.
Identity connectors are used to map your enterprise's identities and group
rosters to the Google accounts and groups used by Google Cloud Search. These
mappings facilitate setting ACLs and search quality hints during indexing.
Next steps
Here are a few next steps you might take:
Several connectors have been built by Google and its partners. For a list of
pre-built connectors, refer to the
Cloud Search connector directory.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-04 UTC."],[],[],null,["By default, Google Cloud Search indexes all of your Google Workspace data.\nYou can also create your own custom program, called a *connector*, to index\ndata stored in a third-party repository. A connector can be a separate program,\na script that runs in its own process, or an add-on to your repository.\n\nThere are two types of connectors: *content connectors* and\n*identity connectors*. Content connectors are used to traverse a repository and\nindex the data so that Google Cloud Search can effectively search that data.\n\nIdentity connectors are used to map your enterprise's identities and group\nrosters to the Google accounts and groups used by Google Cloud Search. These\nmappings facilitate setting ACLs and search quality hints during indexing.\n| **Note:** Alternatively, you can push content from third party repositories directly to the Cloud Search index using the [Indexing API](/workspace/cloud-search/docs/reference/rest/v1/indexing.datasources.items). Integrations of third-party content repositories with the Cloud Search Indexing API can be developed and hosted by content providers, independent system integrators, or Cloud Search customers themselves.\n\nNext steps\n\nHere are a few next steps you might take:\n\n- Several connectors have been built by Google and its partners. For a list of\n pre-built connectors, refer to the\n [Cloud Search connector directory](/workspace/cloud-search/docs/connector-directory).\n\n- For information on how to create a new content connector, refer to\n [Create a content connector](/workspace/cloud-search/docs/guides/content-connector).\n\n- For information on how to create a new identity connector, refer to\n [Create an identity connector](/workspace/cloud-search/docs/guides/identity-connector)."]]
