Appearance
Connecting email
The steps differ by access mode. If you're not sure which one your workspace uses, see Which mode am I on? first — following the wrong set of steps dead-ends at a permissions error.
Organization mode
One admin grants access once, for the whole tenant or domain. Afterwards you attach the specific mailboxes Otto should read.
Microsoft 365
Open Integrations. As the workspace owner, go to Workspace Manager → Settings → Integrations, choose Microsoft 365, select Set up Microsoft 365, then select Connect Microsoft 365.
Sign in as a tenant admin. You'll be sent to Microsoft's admin consent screen at
login.microsoftonline.com. Sign in with an account that holds Global Administrator or Privileged Role Administrator.Review and grant. Microsoft shows the exact permissions Otto is requesting — read and send mail, tenant-wide (the full list, with what each one is for, is on the Security page). Approving here does not attach any mailbox yet; it only authorizes Otto to be attached to the mailboxes you choose next.
If the consent screen labels the publisher "unverified"
Microsoft's publisher-verification badge is a directory listing, not a security control — the app you're approving is still the one Otto's Integrations page sent you to, and the permissions shown are still exact. If your organization's policy blocks consent to unverified apps, a Global Administrator can still grant it, or contact Otto — our verification may simply still be in Microsoft's review queue.
Attach mailboxes. Back in Otto, under Connected inboxes, select Add inbox, enter the mailbox address, and select Add mailbox. Repeat for each mailbox Otto should read. Otto starts watching for new mail immediately once a mailbox is attached.
Choose who can see each inbox. The teammate whose Otto sign-in matches the mailbox address is added automatically. To let anyone else see that inbox's email, select the member count on its row and add them.
Google Workspace
Google's organization mode uses domain-wide delegation instead of an OAuth consent screen — authorized once in the Admin console rather than clicked through.
Get Otto's client ID. In Otto, go to Workspace Manager → Settings → Integrations, choose Google Workspace, and select Set up Google Workspace. The page shows the exact Service account client id and OAuth scopes to authorize.
Copy these from your own Integrations page
Always take the client ID and scopes from that page rather than from any document — including this one. They're rendered live, so they stay correct if Otto's values ever change.
Authorize in the Admin console. As a Super Admin, go to
admin.google.com→ Security → Access and data control → API controls → Domain-wide delegation, add a new API client, and paste in the client ID and scopes from step 1.Connect in Otto. Back in Otto, as the workspace owner, enter your Primary domain and a Verify address (an inbox at that domain). Select Verify connection to check, then Connect Google Workspace. The domain must be the one you sign in to Otto with; Otto support can connect a different one. If authorization hasn't propagated yet, wait a minute and retry — Google's side can lag briefly.
Attach mailboxes. Under Connected inboxes, select Add inbox and add each mailbox address you want Otto to read. Addresses must be at the connected domain. Otto starts watching for new mail immediately.
Choose who can see each inbox. As with Microsoft 365, the teammate whose sign-in matches the address is added automatically; select the member count on a row to add anyone else.
Per-user mode
Both providers work the same way here: each person signs in with their own account and approves access to only their own mailbox. There is no tenant-wide step.
Connecting your own mailbox
Who: owners and admins any time; members once an admin has asked.
Open Integrations. Go to Workspace Manager → Settings → Integrations. Owners and admins always see a Connect my mailbox button here, no request needed.
Sign in and approve. You're sent to your provider's own sign-in screen. Approve the permissions shown — read and send mail on your behalf.
Otto reads the connected address directly from your provider account, so it can only ever be the mailbox you just signed in as. You cannot connect someone else's inbox by typing their address.
Confirm the connection. You're returned to Integrations with your address marked Connected. Otto begins watching your inbox right away.
Asking a teammate to connect
Who: owners and admins.
You can't connect a mailbox on someone else's behalf — only they can complete their own sign-in. What an admin can do is ask:
Request a connection. In Settings → Members, select Request connect next to your teammate's name (the Inbox column shows Not connected). The Team inboxes list on the Integrations page has the same button, plus Request connect for everyone not connected when two or more teammates haven't been asked. Do this for everyone whose inbox Otto should read: members can't start a connection until they've been asked. People who accept an invitation are asked automatically.
They get a prompt. Your teammate gets an email, "Finish setting up Otto — connect your inbox", and a Connect your inbox card on their Otto Home page saying "Your admin asked you to connect it", with a Connect my inbox button. If they select Not now, the card stays hidden in that browser; they can still connect from Workspace Manager → Settings → Integrations.
They sign in. Same as the self-connect flow above: their provider sign-in, their approval, their mailbox only.
Your first connection sets the provider
In per-user mode, the workspace isn't bound to Microsoft or Google until the first person connects. Until then Otto asks which one you use: pick the provider your work email is on. Whichever provider that first person uses becomes the workspace's provider, and everyone else must use the same one.
Google Workspace: if your company restricts outside apps
Many Google Workspace companies only let staff connect apps their IT team has approved. If that applies to you, a Super Admin approves Otto once for everyone (or for a group), before people connect:
Go to
admin.google.com→ Security → Access and data control → API controls → Manage Third-Party App Access.Select Configure new app and search for Otto's client ID:
654869587525-tobl35afpqbgl49lqngt2f83i8gsm701.apps.googleusercontent.comSearch by the client ID, not the name — many unrelated apps are called "Otto". The search returns exactly one app, Otto (Web).
Choose who it applies to (everyone, or the group that uses Otto), set access to Trusted, and finish.
Marking Otto Trusted also removes Google's "Google hasn't verified this app" warning for your users while Otto's Google verification is in progress. Without it, users at companies that allow outside apps can still connect — they see that warning and select Continue.
Next
- Managing team access — reading the roster, disconnecting a mailbox
- Troubleshooting — if a connection didn't complete