Skip to content

Troubleshooting ​

Every message Otto shows when a connection doesn't complete, what it means, and who can fix it.

You can fix these ​

Declined at sign-in ​

Applies to: both modes

You — or your teammate — selected Cancel or Deny on the provider's screen. Nothing changed. Start the connection again and approve every permission requested.

Access blocked by your Google Workspace admin ​

Applies to: per-user mode, Google Workspace

Google stops the sign-in before it reaches Otto, with a message such as "Access blocked: [your company] has not granted access to this app" or Error 400: admin_policy_enforced. Your Google Workspace admin has limited which outside apps can read company mail. Nothing is wrong with your account.

Who fixes it: a Google Workspace Super Admin at your company, once for everyone:

  1. Go to admin.google.com → Security → Access and data control → API controls.
  2. Under App access control, select Manage Third-Party App Access.
  3. Select Configure new app and search for Otto's client ID, 654869587525-tobl35afpqbgl49lqngt2f83i8gsm701.apps.googleusercontent.com. Search by the client ID, not the name — many unrelated apps are called "Otto". It returns exactly one app, Otto (Web).
  4. Choose who it applies to (everyone, or the teams that use Otto), set access to Trusted, and finish.

The change usually takes effect within a few minutes; occasionally Google takes longer. Then try Connect my mailbox again.

Microsoft asks for admin approval ​

Applies to: per-user mode, Microsoft 365

Microsoft stops the sign-in with "Need admin approval" (or "needs permission to access resources in your organization that only an admin can grant"). Your company only lets admins approve outside apps, or Otto has asked for a permission your company hasn't approved yet. Nothing is wrong with your account.

Who fixes it: a Microsoft 365 Global Administrator at your company, once for everyone:

  1. In Otto, go to Workspace Manager → Settings → Integrations and select Connect my mailbox. If your own mailbox is already connected, select Disconnect first, then Connect my mailbox.
  2. On Microsoft's permission screen, tick Consent on behalf of your organization, then select Accept.
  3. Your teammate tries Connect my mailbox again. The approval screen no longer appears.

If the checkbox isn't there, the account signing in isn't a Global Administrator; ask whoever is. Otto also won't appear under App registrations in Entra, which only lists apps your own company built; once anyone has tried to connect, it shows under Enterprise applications.

If you approved Otto in the Entra admin center instead ​

Microsoft also offers a button for this in the Microsoft Entra admin center: Enterprise applications → Otto → Permissions → Grant admin consent for your company. It unblocks your teammates too, but it approves every permission the Otto app can request. That includes organization mode's application permissions, which let Otto read and send from every mailbox in your company. Per-user mode never uses them (see What Otto can access), so we recommend the in-Otto approval above.

If you already used the Entra button, nothing changes in how Otto behaves, but you can take the extra access back without disconnecting anyone:

  1. In the Entra admin center, open Enterprise applications → Otto → Permissions, on the Admin consent tab.
  2. For each permission whose Type is Application (Mail.Read, Mail.ReadWrite, Mail.Send, User.Read.All, MailboxSettings.Read), select it and choose Revoke permission.
  3. Leave the Delegated permissions in place: those are the ones connected mailboxes use.

"Google hasn't verified this app" ​

Applies to: per-user mode, Google

Google shows this while Otto's Google verification is in progress. It is expected: select Advanced → Go to Otto (or Continue) and approve the permissions. To remove the warning for your whole company, a Google Workspace Super Admin marks Otto Trusted — see Access blocked by your Google Workspace admin.

Your admin hasn't asked yet ​

Applies to: per-user mode

Otto says "An owner or admin has to ask for your inbox first". You tried to connect without a pending request, and you aren't an owner or admin. This is Otto's own step, not Microsoft's or Google's: an owner or admin selects Request connect next to your name in Settings → Members, then you try again from the Connect your inbox card on your Home page or from Integrations.

This also applies if you disconnected your own mailbox earlier: a member needs a new request to connect again.

Already connected to the other provider ​

Applies to: per-user mode

Your workspace is bound to Microsoft or Google by whoever connected first — one provider per workspace. Use that provider instead, or ask Otto support to reset the binding if it's genuinely wrong.

No offline access granted ​

Applies to: per-user mode

The provider didn't return a long-lived token, so the connection would have expired within the hour. Try again and make sure you approve all requested permissions, not a partial set.

Sign-in exchange refused / Couldn't read your mailbox ​

Applies to: both modes

A transient failure completing the sign-in. Simply try again.

Applies to: both modes

The link from Otto is only valid for about 10 minutes, or the sign-in tab was left open too long. Start the connection again from the Integrations page — don't reuse an old tab or bookmark.

Only a workspace owner can connect Microsoft 365 ​

Applies to: organization mode

Connecting Microsoft 365 or Google Workspace for the whole organization is owner-only in Otto. Ask an owner to run it, or ask an owner to make you an owner in Settings → Members.

Already connected to a different Microsoft 365 account ​

Applies to: organization mode

Your workspace is tied to a different tenant. Remove all attached mailboxes, disconnect the existing tenant, then reconnect the correct one.

Microsoft didn't grant the permissions Otto needs ​

Applies to: organization mode

The signed-in account approved only some permissions, or lacked admin rights to approve them all. Retry with a Global Administrator account and approve everything shown.

Contact Otto support ​

Something isn't set up right on our side ​

Applies to: both modes

A required piece of Otto's own configuration is missing — credentials, an encryption key, or the connection-link secret. This is on Otto, not your account, and retrying won't help. Send us the workspace name and the time you saw it.

Something went wrong while connecting ​

Applies to: both modes

An unexpected server error. If it persists past a second try, let us know.

Revoking access at the source ​

Disconnecting inside Otto is usually enough — it deletes the stored token. To additionally revoke at the provider, or if the person has already left and can't disconnect:

Provider and modeWhere to revoke
Microsoft, organizationEntra ID → Enterprise applications → remove Otto
Microsoft, per-userThe individual's own My Apps → remove Otto
Google, organizationAdmin console → API controls → Domain-wide delegation
Google, per-userTheir Google Account → Third-party access

Questions this guide doesn’t answer — contact Otto support. · Privacy policy