Google Drive

The Google Drive integration indexes one folder or shared drive into Knowledgebase. Once connected, Keldyn reads the documents in that folder on a schedule and turns them into searchable, cited passages — so a policy or design note in Drive can be found without leaving Keldyn. This is a knowledge connector. It does not collect control evidence. For IAM and Workspace identity evidence, use the separate Google Cloud integration.

​

What it’s used for

Keldyn uses Drive as a source of organisational documents: policies, procedures, architecture notes, and other files your team already keeps in a shared folder. After the first sync, those files appear under Drive in the Knowledgebase index browser, and questions in Knowledgebase or AI Chat can cite them with a link back to the file in Drive. Choose a folder that is already meant to be shared with compliance and security reviewers. The folder — not the Google account — is what limits what Keldyn reads.

​

Before you begin

​

Set up the integration

​

What Keldyn indexes

Keldyn indexes files it can turn into readable text. Everything else is skipped rather than force-converted — a spreadsheet flattened into garbled text would pollute every later search. Nested subfolders are included. A file that cannot be read (for example, access withdrawn on one document) is recorded against that file; the rest of the folder still syncs.

​

What data Keldyn collects and why

Keldyn requests read-only access and never writes to Drive. It collects only the data needed to search and cite the files you selected.

​

Permissions and scopes

Keldyn requests these OAuth scopes. All are read-only. The Drive scope is account-wide. The folder you select is what stops Keldyn walking the rest of My Drive. If no folder is set, the connector reports that it is not configured and does not list or download anything.

​

Who can read indexed files

Anyone on the team who can open Knowledgebase can read every file from the connected folder, including files that were shared only with a few people in Drive. Source-side sharing settings do not carry over. See Knowledgebase privacy. If a file should not be searchable, keep it out of the connected folder, or use Remove from index in the Knowledgebase browser. Removing it from the index does not delete it from Drive.

​

Keeping the index current

Keldyn checks the folder about every five minutes and re-reads files that changed since the last successful sync. You can also trigger an immediate pull with Sync now.

• Editing a file in Drive updates its passages on the next sync.
• Moving a file out of the folder, trashing it, or withdrawing access unpublishes it. It stops appearing in search; an existing citation still resolves.
• Reconnecting forces a full re-read, which is how a file that previously failed conversion gets another attempt.

​

Troubleshooting

A search that should have hit a Drive file usually means one of the following:

• No folder selected — the connector is connected but indexes nothing until you choose a folder.
• Unsupported type — spreadsheets, slides, and files over 25 MB are skipped.
• Wrong Google account — Keldyn can only read what the connecting account can open.
• Reauth required — access was revoked in the Google account. Select Reconnect, and if Google does not return a refresh token, remove Keldyn’s access in your Google account permissions first, then connect again.

​

Next steps