The intended connection
We are planning a Google Drive source connection so teams can bring selected business documents into Steer. The intended starting point is explicitly chosen files, with Google Docs, Sheets and Slides evaluated as document sources. This integration is not available yet. Tell us which Workspace material matters to your team when you join the waitlist.
What this can help with
- Intended use: make a selected Google Docs playbook available as company reference.
- Intended use: connect the approved product narrative maintained in Slides.
- Intended use: reference documented assumptions from an explicitly selected Sheet.
Register your interest
- Join the waitlist and select Google Drive as an integration you need.
- Describe the files and shared-drive setup your team uses.
- We will confirm supported scope and onboarding requirements when the integration is ready.
Scope and availability
- Planned; no current connection or delivery date is promised.
- File-by-file selection does not imply recursive folder or whole-Drive access.
- Google permission verification, document extraction and revocation must pass before availability is announced.
Steer is onboarding companies in stages. Join the waitlist to discuss your setup. Read about access and accountability.
What to check before connecting
For any Drive connection, distinguish the files selected, the permissions requested and the actions the application performs. Steer’s planned starting point is selected documents, without source write-back.
- Check whether selection means individual files, folders or a whole Drive. Do not infer recursive access from a file picker.
- Google’s drive.file scope narrows access to files shared with the app, but is not inherently read-only: it can permit file creation and modification. Evaluate application behaviour separately from OAuth scope.
- Broader Drive read access uses restricted scopes with additional verification requirements. Confirm the exact scope before granting it.
- Test Google Docs, Sheets and Slides extraction, source updates, withdrawal of file access and connection revocation before including important material.
Google’s Drive scope documentation documents the platform capability; it does not verify Steer availability.
Plan the context, ownership and access
Check permissions and ownership, test source updates and evaluate the connection in a real task.