layman/terms
Apps talking to apps

“Sign in with Google” (OAuth)

oh · awth

In shortSigning in to an app by letting another account, like Google or Apple, vouch for you, without sharing your password.

You click “Sign in with Google” and you're in. The new app never saw your Google password. That's OAuth at work.

A friend who’s a member at a club can vouch for you at the door: “They’re with me.” You get in. Your friend never handed over their membership card.

“Sign in with Google” works like that. Instead of creating a new password, you let a trusted account, like Google, Apple or Microsoft, vouch for you. The technical name for how this works is OAuth.

What happens

Why it’s handy

You have fewer passwords to remember. The app never holds your password either. It’s also how one app gets permission to work with another, like a scheduling app reading your calendar.

What it isn’t

It isn’t giving the app your Google account. It gets limited permissions, which you can take back in your Google, Apple or Microsoft settings at any time.

Where the comparison breaks down

A friend vouches once at the door. With OAuth, the app may keep its access for months, until you remove it.

How the words fit together

OAuth grants permissions without sharing passwords. It’s how many integrations get access to your accounts.

Watch out

Read what an app asks for when you click “Sign in with…”. “See your email address” is normal. “Read and send your emails” is a lot.

When you'll hear it

“Just use Google sign-in.” Sign in with your Google account instead of making a new password.

“Revoke its access.” Go to your Google or Apple settings and stop that app from using your account.

“It needs these scopes.” These are the exact things the app is asking to see or do.

Say it in a meeting

“Which apps have access to our company accounts through “Sign in with…”? Do they all still need it?”