The Problem With Traditional OAuth
Most SaaS platforms treat login and service connections as two separate flows. You sign in with Google to create your account. Then you go to Settings. Then you click "Connect Google" again. Then you approve a second set of permissions. Then you configure which property, which calendar, which mailbox.
That's five steps to do what should be one. And most users never complete it.
How 0nCore Does It Differently
When you click "Continue with Google" on 0nCore, we request extended scopes — Analytics, Gmail, Drive, Sheets, Calendar — in the same OAuth flow. Your sign-in IS your service connection. One click, everything wired.
The auth callback automatically bridges the OAuth token into a user_connections table. The same token that authenticates your session also grants API access to your Google services. No second flow. No settings page required.
The Technical Architecture
Every OAuth provider (Google, LinkedIn, Slack, Facebook, GitHub) follows the same pattern:
- User clicks sign-in button with provider
- Supabase handles the OAuth flow
- Auth callback bridges the provider token to
user_connections - Dashboard reads from
user_connectionsfor API access - Token refresh happens automatically via cron
The user never touches a settings page. They sign in, and their services are connected.
Why This Matters for Retention
The #1 reason users abandon a SaaS product is setup friction. Every additional step in onboarding is a 20-30% drop-off. By collapsing sign-in and service connection into one step, 0nCore eliminates the biggest friction point in the entire funnel.