Reading a mailbox is a restricted permission

Google sorts what an app can ask a Gmail user for into tiers. Sending an email on someone’s behalf is sensitive. Reading their mailbox is restricted, the highest tier, because a business mailbox holds the day-to-day of the business: customers, orders, quotes and invoices.

An app can only ask the public for a restricted permission once Google has reviewed exactly how it will use the mail, and once an independent assessor has tested its security. That test is the Cloud Application Security Assessment, CASA, set by the App Defense Alliance. It is not a form to fill in and it is not a one-off: it is repeated every year for as long as the app keeps the access.

What the assessment tested

The assessment was run by TAC Security, one of the labs authorised to carry it out, against 48 requirements drawn from the OWASP Application Security Verification Standard. Each one needed evidence: a configuration, a test result, a log, a policy. Among them:

It did not pass first time

The first review came back with eleven requirements needing more. Most asked us to prove something Inbox already did, with a dated report or an excerpt rather than a description. A few asked for more than we had, and we built it. We answered every point, and on 26 October all 48 requirements passed. Google approved the access on 30 October.

Google does not hand out access to people’s mail. It is earned through an outside test, and earned again every year.

Reply from Gmail, and the team still sees it

This is the part a team will notice most. Until now, a reply sent from Gmail itself never reached Inbox: the customer had their answer, but the conversation in Inbox still showed them waiting, and nobody else on the team could see what had been said.

Now, when you reply to a customer from the connected mailbox in Gmail, on your phone or at your desk, that reply is added to the customer’s conversation in Inbox within a minute or two. Whichever app the answer came from, the record is whole and the whole team can see it. It works for replies to customers Inbox already knows, sent from the connected address: a new email written in Gmail doesn’t open a conversation, and mail sent from someone’s own address stays theirs.

What Inbox reads, and what it doesn’t

Connecting asks for two Google permissions, gmail.readonly and gmail.send. With them, Inbox reads:

It never reads drafts, labels, contacts or anything else in your Google account, and it never changes, moves or deletes anything in your mailbox. Gmail data is not used for advertising, and it is never used to train general AI models. You can disconnect in Settings at any time, or remove the access from your Google account. If you would rather Inbox didn’t read your mail at all, leave the read box unticked: Inbox then only sends your replies, and new mail reaches it by forwarding, as before. The full detail is in our privacy policy.

What changes day to day

Sign up with your Gmail or Google Workspace address, sign in with Google, and tick both boxes. New email to that address appears in Inbox within a minute or two. Replies you send from Inbox go out from your own address, with a copy in your Gmail Sent folder. Outlook and Microsoft 365 already work this way.

If you already use Inbox with a forwarding rule from Gmail, Settings now shows how to connect. Once you have, the rule can go, and if you leave it on, nothing arrives twice.