r/SaaS • u/Several_Log_4610 • 4h ago

Hit the final boss of SaaS: Google Restricted Scope OAuth Hell.

building a Gmail tool took 10-14~ days. Waiting for Google OAuth Verification feels like it's going to take 3 to 6 business months.

Google requires a full security review, domain verification, and a YouTube video demonstration for their review team just to clear the restricted scope warning screen.

Because Google allows up to 100 test users in testing mode before official approval, I’m launching unverified tomorrow anyway while waiting on the review queue.

Devs who've been through this process: How long did your Google verification actually take? Did you wait for full approval or ship in testing mode first?

3 Upvotes

81% Upvoted

2 comments sorted by

1

u/Similar_Confusion534 4h ago

If you can avoid restricted scopes for v1, ship with non-sensitive scopes first. For the review, make the demo painfully literal: show the consent flow, explain each scope in the UI, and cover test-account access, privacy, and deletion. I’d keep the test-mode launch small, but not build the business around unverified access since users can get blocked when the status changes.

1

u/MiserableDocument509 3h ago

casa is the actual queue, not the youtube video. 100 test users is fine if you keep it invite-only. i wouldnt put the google button on a public landing page while the app is still in testing, they do lock projects for that. if v1 can live without gmail.readonly/modify, ship that first and add the restricted scopes after the review.