Google Drive
A Google Workspace super admin connects Google Drive with domain-wide delegation so nima can read shared-drive and company-wide documents.
Connecting Google Drive lets nima read your company's shared documents, so people can ask about them in Slack or over MCP. A Google Workspace super admin sets it up once. There is no per-user sign-in, and nothing for other employees to do.
nima only reads. It never edits, shares or deletes a file. Everyone in your nima workspace can ask about what nima read, so connect only drives you are happy to share with the whole workspace.
What nima reads
nima reads two kinds of files:
- Files in the shared drives that the indexing account is a member of.
- Files shared with your whole company (your Workspace domain).
nima reads these file types:
- Google Docs, as text.
- Google Slides, as text.
- The first sheet of each Google Sheet.
- Plain text and Markdown files.
nima never reads anyone's private files, or files shared only with specific people or groups. It does not read PDFs, images, or uploaded Word, Excel and PowerPoint files.
nima syncs once a day. A file you delete or stop sharing is removed from nima within a week.
Before you start
You need:
- A Google Workspace super admin.
- An account for nima to read as. Use a dedicated account, such as
nima-index@yourcompany.com. Add it as a member of each shared drive you want nima to read. Viewer is enough.
Consumer gmail.com accounts are not supported.
Step 1: Get nima's client ID
In the nima web app, open app.getnima.io, go to Integrations, choose Google Drive, and click Set up. The panel shows nima's client ID and the scope to authorize, each with a copy button, and the Admin console steps. Copy the client ID.
Step 2: Authorize nima in the Google Admin console
Open admin.google.com and go to Security, then Access and data control, then API controls.
Choose Manage Domain Wide Delegation, then Add new.
For Client ID, paste the client ID from step 1.
For OAuth scopes, enter exactly this one scope:
https://www.googleapis.com/auth/drive.readonlyClick Authorize.
Step 3: Connect
On the same panel, enter the indexing account, for example nima-index@yourcompany.com, and click Connect. nima checks the setup before it saves anything, then starts the first sync.
Step 4: Verify
Click Verify on the Google Drive panel at any time. nima re-runs its checks and shows each one as pass, warning or fail, with the fix next to it. Use the table below to understand each check.
| Check | If it fails |
|---|---|
| nima side configured | Contact nima support. |
| Google Workspace account | gmail.com and googlemail.com addresses are refused. Use an account in your company's Workspace domain. |
| Delegation authorized | The error says "not authorized". Check the client ID and that the scope is exactly drive.readonly. Google usually applies changes within minutes, and at most within 24 hours. |
| Indexing account active | The account does not exist or is suspended. Check it in the Admin console. |
| Shared drives visible (count) | A count of 0 means the account is not a member of any shared drive. Add it to the drives you want nima to read. |
| Files shared with the whole company (count) | Informational. These files are read as well. |
| Supported files found (count) | Informational. This is how many files nima will index. |
Below the checks, the panel lists what will and will not be indexed. What nima will index: supported files in the shared drives the account belongs to, and supported files shared with the whole company. What it will not index: private files, files shared only with specific people or groups, and unsupported file types.
After you connect
The first sync takes longer for a large Drive. To check progress, ask nima in Slack:
What's the status of the Google Drive sync?
The status is reading, synced or stalled.
Once it has synced, ask questions in Slack or through MCP. Answers link to the source document.
Change or remove
- Change the indexing account. Enter the new email on the panel and click Connect again. nima replaces the old index.
- Disconnect. Remove the client ID in the Admin console, or click Disconnect on the Google Drive panel (an admin of your nima workspace can do this). If you only remove the client ID, nima marks the connection invalid at the next sync. When you disconnect from nima, the indexed copies and the knowledge learned from them are removed.
Security
nima signs short-lived access tokens with a Google service account that nima owns. nima stores no passwords, keys or refresh tokens from your company. You can revoke access at any time by removing the client ID in the Admin console.
Troubleshooting
The verify table above covers setup problems.
It worked, then stopped. The delegation was removed, or the indexing account was suspended. Click Verify to see which.