← Integration Engineering
Integration Engineering

Whose Name Is on the “Allow Access” Screen?

14 Oct 2026·3 min read

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.

Why the business side caresYour own name on the consent screen means fewer people stop halfway, and fewer "is this safe?" tickets.
Do this in 60 secondsClick one of your own "Connect" buttons and stop at the consent screen. Read the name and permissions as a customer would. If the name is not yours, or it asks for more than the feature needs, that is your next task.
Today’s AI angleWith your own app, you can ask only for the scopes your AI agent’s tools need. If the agent misbehaves, the damage stays inside those scopes.
Whose Name Is on the “Allow Access” Screen? · Ali Huzaifa