Glossary
What is OAuth sign-in?
OAuth sign-in, often called social login, lets you log in to a site with an existing account such as Google, GitHub, X or LinkedIn instead of creating a password. The site gets a verified identity and limited permissions you approve. Many directories offer it; it speeds up sign-up and reduces passwords to manage.
How it works
- You click "Sign in with Google" (or another provider).
- The provider asks you to confirm and shows the requested permissions.
- The site receives a token proving your identity and the approved data, such as your email.
OAuth 2.0 handles authorisation; OpenID Connect adds the identity layer most sign-ins use.
On directories
Of the 352 directories we checked, 70 required an account. Many offered Google, GitHub or X sign-in. Using one consistent provider for launch accounts makes them easier to manage later.
For agents
If you're already signed in to the provider in your browser, an agent can click through the OAuth flow, but the consent screen is a decision: review which permissions you grant. Agents shouldn't type your provider password.
Example
A founder uses "Sign in with GitHub" across developer directories. Her agent clicks the button, she approves the first consent screen for each new site, and the agent fills the rest.
FAQ
Is social login safe?
Generally, yes; check the permissions requested.
What is the difference between OAuth and OpenID Connect?
OAuth grants access; OpenID Connect adds a standard identity layer for sign-in.
Can I revoke access later?
Yes, from your provider's connected apps settings.