Connecting Gmail or Outlook

For Lakewave users and the IT admins who approve apps for them
Last updated: October 17, 2026
In plain terms. Connecting a mailbox lets Lakewave send the emails you approve from your own address. Lakewave asks only for permission to send mail and to read your name and email address. It cannot read, search, or delete anything in your inbox. Many companies let you connect in one click. Some require an IT admin to approve Lakewave once for the whole organization first; the admin section explains how, and takes about two minutes.

1. How to connect

  1. Sign in to app.lakewave.ai and open Connections.
  2. Click Connect Gmail (Gmail or Google Workspace) or Connect Outlook (Outlook.com or Microsoft 365).
  3. Sign in on Google's or Microsoft's own page with your usual email password and multi-factor prompt. Lakewave never sees your password.
  4. Review the permissions and click Allow or Accept. You return to Connections with the mailbox listed.

You can connect more than one mailbox. Lakewave rotates sends across connected mailboxes and keeps each one within a safe daily volume.

2. What Lakewave can and cannot access

ProviderPermission requestedUsed for
Googlegmail.sendSending emails you approve, from your address
Googleopenid, userinfo.email, userinfo.profileShowing which mailbox is connected
MicrosoftMail.Send (delegated)Sending emails you approve, from your address
MicrosoftUser.Read (delegated)Showing which mailbox is connected
Microsoftoffline_accessKeeping scheduled emails sending without signing in again each day

Lakewave does not request permission to read, search, move, or delete mail, contacts, calendars, or files. Replies to your emails arrive in your own inbox as usual. Connection tokens are stored encrypted, and you can revoke them at any time (Section 6). Lakewave is published by Lynbrook Solutions LLC, a Microsoft verified publisher, and its Google integration has completed Google's OAuth verification. See our Privacy Policy for details.

3. If your company blocks the connection

Company accounts are controlled by your IT team. You may see one of these:

Nothing is wrong with your account. Your IT admin needs to approve Lakewave once, and after that everyone at your company connects in one click. Email my IT admin opens a ready-to-send email with these instructions (the same button is on the Connections page in Lakewave). You can also send your admin a link to this page. If Microsoft shows a Request approval button, use it; the request goes straight to your admin's queue.

4. For IT admins

Approving Lakewave lets users in your organization connect their own mailboxes with the send-only permissions listed in Section 2. Each user still signs in and connects their own mailbox; approval does not connect any mailbox by itself and does not give Lakewave access to anyone who has not connected.

Publisher: Lynbrook Solutions LLC (Microsoft verified publisher)
Microsoft application (client) ID: 8af64d54-fda0-4ee2-97f0-5cecb93300f2
Google OAuth client ID: 3134128675-6o6dgodna8jf61h47s1uddno9plm9p4b.apps.googleusercontent.com

4a. Microsoft 365 admin approval

A Global Administrator, Cloud Application Administrator, or Application Administrator can approve Lakewave for the whole tenant in one step:

Approve Lakewave for my organization

Sign in with your admin account, review the permissions, and click Accept. You return to Lakewave with a confirmation. To review or remove the approval later, open the Microsoft Entra admin center, go to Enterprise applications, and select Lakewave.

If your organization uses the admin consent workflow, you can instead approve the user's request from Enterprise applications > Admin consent requests. If you restrict which users may use the app, assign the users or groups who need it under Lakewave > Users and groups.

4b. Google Workspace admin approval

A super admin, or an admin with Security settings privileges, can mark Lakewave as trusted:

  1. In the Google Admin console, go to Security > Access and data control > API controls.
  2. Under App access control, click Manage Third-Party App Access, then Add app > OAuth App Name Or Client ID.
  3. Search for the Google OAuth client ID above, select Lakewave, and choose the organizational units that should have access.
  4. Set access to Trusted and click Finish.

Changes usually apply within minutes but can take up to 24 hours. If your organization only blocks apps that request restricted scopes, no action may be needed; gmail.send is a sensitive scope, not a restricted one.

5. Approving before a team rollout

For teams rolling Lakewave out to several reps, approve Lakewave using the steps in Section 4 before reps connect. That avoids each rep hitting an approval screen. If you are working with a Lakewave contact on onboarding, we can walk your IT team through it on a short call.

6. Disconnecting and revoking access

7. Contact

Questions about connecting a mailbox: [email protected]
Security reviews and questionnaires: [email protected]