Adding social login (Google, Apple, GitHub)
Let users sign in with their existing accounts. One click, no password to remember.
Most users prefer signing in with an account they already have over creating a new password. OverSkill makes it one prompt.
How sign-in works on OverSkill (important)
OverSkill apps all share one platform-managed login system. When your app uses OverSkill's built-in authentication, sign-in is handled centrally by OverSkill — you don't configure OAuth providers, register a developer account anywhere, or paste in any keys, and there's no per-app or per-workspace switch to turn a provider on
for just your app. If a provider is live on the platform, your app can use it automatically; if it isn't live platform-wide yet, it can't be enabled for a single app.
That means: nothing to set up on your end, and nothing support can unlock
for your specific workspace — availability is the same for every app.
Providers you can offer today
- Google — ✅ live now, platform-wide. Covers most Gmail users and Google Workspace teams.
- GitHub — ✅ live now, platform-wide. Common for developer-facing tools.
- Apple — ⏳ rolling out. Apple sign-in is not yet available across the whole platform; it's coming and will be available before OverSkill leaves beta. Until then, use Google/GitHub (and email/password).
You can offer one, several, or all of the available providers — alongside or instead of email/password.
Adding it
Just ask in the editor:
Add Google sign-in.
Add Google and GitHub sign-in. Keep email/password as an option too.
Done in about 30 seconds. Your users see the social buttons on the sign-up and login screens. (If you ask for Apple sign-in before it's live platform-wide, it won't appear yet — that's expected, not a bug in your app.)
What it looks like to your users
When someone clicks Sign in with Google
:
- Google's standard sign-in screen opens
- They pick which account to use (or sign in)
- Google asks
Allow [Your app] to see your name and email?
- They click Allow
- They're in
GitHub works the same way. Users never leave your app for long — the whole flow takes a few seconds.
What you get from social login
For every user who signs in with a social provider, you get:
- Their email (so you can contact them)
- Their name (so your app feels personal)
- A profile photo (some providers — used for avatars)
That's it. You don't get their contacts, files, or anything else.
Setup required from you
None. OverSkill handles all the technical setup automatically for the providers that are live. You don't need to register a developer account anywhere or paste in keys.
Setup required from your users
None. If they already have a Google or GitHub account, they can sign in.
When users want to switch methods later
If someone signs up with Google and later wants to use email/password instead, they can:
- Stay signed in with Google
- Go to their profile settings
- Click Add a password
Now they can use either.
What to read next
- How your app's users sign up — the broader sign-in setup
- Restricting access to paid users — gate features behind payment