Whose Name Is on the “Allow Access” Screen?
Your customer clicks "Connect Google Calendar", and the Google screen says a company they have never heard of wants to read their calendar. Many will stop right there. That name does not come from your product. It comes from the OAuth app behind the button.
What an OAuth app is
You register an app in the provider’s developer console. You give it a name, a logo, the allowed redirect URLs and the scopes it may ask for. You get back a client ID, which is public, and a client secret, which is not.
Shared app or your own
A shared app is one registered app used by many companies. It is quick, and you can test on day one. With your own app:
- Your company’s name and logo appear on the consent screen.
- You choose the scopes, redirect URLs and settings yourself.
- Rate limits and provider reviews belong to your app, not shared with others.
Reviews take time. Google’s docs, for example, say apps asking for sensitive scopes, like reading Calendar events, may have to pass verification first. So register your own app early, even while you test on a shared one. Most teams move to their own before going live with customers.