Google OAuth checks can slow down a Gmail-based SaaS launch
A SaaS that reads Gmail, changes Gmail data, and helps compose messages must pass Google’s OAuth . The requested are gmail.readonly, gmail.modify, and gmail.compose, and all three are in Google’s restricted tier. The app setup, OAuth consent screen, public , live homepage, and brand are already done.
The next step is recording a so Google can see how the app uses Gmail access in practice. The main unknowns are the real approval timeline, the cost and timing of the , what Google expects in the , and what mistakes can cause rejection.
Key points
- Gmail read, modify, and compose access puts a SaaS into Google’s stricter OAuth review path.
- gmail.readonly, gmail.modify, and gmail.compose are restricted .
- The basic setup includes an OAuth consent screen, , homepage, and brand .
- The may be a major approval point because it shows how Gmail access is actually used.
- s should plan for review time, possible rejection, and cost before launch.