OAuth is an open standard that lets one application access another on a user's behalf through tokens, without the user sharing their password. When you connect a tool to another service, for example by choosing to allow it to read your calendar, OAuth issues the tool a token with defined permissions, called scopes, instead of giving it your credentials.

This is safer than handing over a password, and it lets you limit what the tool can do and revoke its access later. OAuth is about authorization, meaning what an application may do, rather than proving who you are, which is handled by related standards built on top of it.

OAuth tokens are valuable. Anyone who obtains one can use the permissions it carries until it expires or is revoked, and broad scopes increase the harm of a stolen token. Some tokens last a long time, and approving an integration can quietly create lasting access.

To manage the risk, grant the narrowest scopes needed, review connected applications regularly, remove those that are no longer used and revoke tokens after a suspected compromise. Vendors should store tokens securely, keep lifetimes short and make revocation easy.