1. Overview and control
Connecting Google is optional. If you connect, Office Intelligence requests the permissions listed below so its agents can work with Drive, Gmail, Calendar, Sheets, Docs, Slides, Contacts, and Tasks when you ask. Google shows the permission request before you authorize it. You can decline, disconnect Google in Office Intelligence, or revoke access from your Google Account.
Access is used to provide the features you request, not for advertising. An agent should access Google data relevant to the task you give it. Some actions that change or send information require confirmation in the application. Review the requested permissions carefully before authorizing them.
2. Permissions requested
The Office Intelligence Google connection requests the following OAuth scopes. A scope permits the described type of access; the task you request determines which data is actually used. This connection requests the Workspace permissions together rather than asking separately for each service.
Google connections created for Agent Builder integrations are separate. Depending on the connector selected, those flows may additionally request https://www.googleapis.com/auth/drive for Drive integration features or https://www.googleapis.com/auth/calendar for Calendar integration features, alongside the relevant scopes listed above. The integration’s Google authorization page shows the permissions requested for that connection.
| OAuth scope | Data accessed | Why it is requested |
|---|---|---|
| openid, email, profile | Google account identifier, email address, and basic profile information. | Identify the connected Google account and show which account is connected. |
| https://www.googleapis.com/auth/drive.readonly | Drive file names, metadata, and file contents that the user requests the agent to find or read. | List, search, and read existing Drive files. The narrower drive.file permission does not provide general access to browse the user’s existing Drive files. |
| https://www.googleapis.com/auth/drive.file | Files created or opened through the application. | Create and manage files the user chooses to save from Office Intelligence to Google Drive. |
| https://www.googleapis.com/auth/gmail.readonly | Gmail message content, labels, and relevant message metadata. | Find, read, and summarize messages when the user asks the agent to work with email. |
| https://www.googleapis.com/auth/gmail.modify | Gmail messages and labels, including changes the user requests. | Support requested mailbox actions such as changing message read or label state. |
| https://www.googleapis.com/auth/gmail.compose | Draft message content created by the user or agent. | Create or manage drafts when the user requests email composition. |
| https://www.googleapis.com/auth/gmail.send | Message content and recipient information for messages the user asks to send. | Send user-requested messages. Sending or other consequential account changes require user confirmation in the product. |
| https://www.googleapis.com/auth/calendar.events | Calendar event details and event changes requested by the user. | Find, create, and update calendar events without requesting broader calendar access. |
| https://www.googleapis.com/auth/spreadsheets | Spreadsheet names, contents, and edits relevant to the requested task. | Find, read, create, and edit Google Sheets as requested by the user. |
| https://www.googleapis.com/auth/documents | Google Docs content and document changes relevant to the requested task. | Read, create, and edit Google Docs as requested by the user. |
| https://www.googleapis.com/auth/presentations | Google Slides content and presentation changes relevant to the requested task. | Read, create, and edit Google Slides as requested by the user. |
| https://www.googleapis.com/auth/contacts | Google Contacts information relevant to the requested task. | Find or manage contacts when the user asks the agent to work with contacts. |
| https://www.googleapis.com/auth/tasks | Google Tasks lists and task details relevant to the requested task. | Find, create, and update tasks when the user asks the agent to manage tasks. |
3. Processing and storage
To keep the Google connection available, the service stores an encrypted Google refresh token in its database. It obtains an access token for a request and passes it to the Office Intelligence worker for that request. Tokens are not intended to be included in prompts or application logs.
When needed to complete your requested task, relevant Google content and your prompt are processed by the AI provider configured for Office Intelligence. The worker currently defaults to DeepSeek; a deployment or agent configuration may use another supported provider. Provider handling is subject to that provider’s applicable terms and settings. Denbegnaye AI does not use Google user data to train generalized AI models.
Google information is used to provide or improve user-facing features you request, for security, and as required by law. It is not sold or used for advertising. For further information about account data, content, providers, retention, and security, see the Privacy Policy.