Skip to content
Module
Tech

What is OAuth 2.0? Definition for product teams

OAuth 2.0 is a protocol for delegated access: it lets an application act on a user's data in another service without ever seeing their password. The user is sent to that service, signs in, reviews the requested permissions (the scopes) and approves them. The application then receives an access token limited to those scopes and to a set lifetime, which the user can revoke.

Definition written by Alex Dionisio, Senior Product Manager. Updated November 13, 2026.

Why it matters for a PM

As soon as a product connects to its users' calendar, inbox, CRM or file storage, OAuth is involved. The consent screen is part of the user journey: asking for too many scopes scares people off, asking for too few blocks the feature. The PM also has to plan what users see when access expires or is withdrawn, and any review a provider requires before certain scopes can be offered to the public.

Example

A scheduling tool wants to read availability from Google Calendar. The PM limits the request to busy time slots rather than full calendar access. More users accept the consent screen, and the team adds a clear prompt asking people to reconnect their account if the token is revoked.

Key points

  • OAuth 2.0 grants access; OpenID Connect builds on it to tell the app who the user is, for sign-in.
  • Scopes define exactly what the application is allowed to do.
  • Access tokens expire; a refresh token gets new ones without asking for consent again.
  • Users can revoke access from the third-party service at any time.

Common mistakes

  • Requesting every scope at first sign-in instead of asking when each one is actually needed.
  • Forgetting the reconnection flow for revoked or expired tokens.
  • Using plain OAuth as proof of identity without OpenID Connect.

Go further with Module

The courses and lessons that cover this concept:

Guides on this topic