Google Workspace

Let Nebula read Gmail and Drive, and send Gmail messages you ask for, through a per-member OAuth connection.

On this page

What it does

With your consent, Nebula can read your Gmail and Drive files, and send Gmail messages when you explicitly ask it to.

A Google account. Each member connects their own.
Your organization’s Google connector set up by a BreachLine administrator. Signing in to BreachLine with Google does not, by itself, grant Gmail or Drive access.

In Settings, Integrations, choose Google (Gmail / Drive) and connect.
Review Google’s consent screen and approve.
Ask Nebula to list something (for example recent messages) to confirm the connection. Do not send a test email unless you mean to.

BreachLine requests exactly these Google scopes:

Scope	Allows
`gmail.readonly`	Reading Gmail.
`gmail.send`	Sending Gmail messages you request.
`drive.readonly`	Reading Drive files.

It does not request mailbox changes or deletion, draft management, Calendar access or Drive writes.

The connection is personal: only the member who connected it can use its mail and files. Being in the same organization does not share another member’s mailbox.
Access is offline (a refresh token) so work can continue while you are away. Google can expire or revoke tokens; reconnect when asked.
The connection list shows whether Google reported the granted scopes. If it did not, BreachLine treats the granted capabilities as unknown rather than assuming full access.

Symptom	Check
Connect is refused	Consent was completed. A callback without a refresh token is rejected, so retry the consent screen.
Access stops working	Reconnect; the token may have expired or been revoked in your Google account.