Add us to your Google project

Do this only if you bought done-for-you, or you are about to. DIY buyers do not need to add us.

Add OAuth Config Editor. Do not add Owner.

Google does not require our email to be Owner. To prove a domain, Google’s sensitive-scope page says to use a Google account that is an Owner or an Editor of the Cloud project. That account should be yours. It does not have to be the only Owner, and it does not have to be our email.

Google’s permission list gives oauthconfig.verification.submit to the role named OAuth Config Editor. That is the smallest role we found that can edit the sign-in screen and submit the check. The broad Owner role can also delete the project and change billing. The broad Editor role can change most of the project. We do not need either of those for our email.

Google marks OAuth Config Editor as Beta. If the role box does not offer it, stop and email us. Do not switch to Owner unless we have confirmed the smaller role is missing and you agree in a reply. Source: OAuthConfig roles (page updated 4 November 2026).

This role can see OAuth client secrets stored in the project. That is still much smaller than Owner. Do not also email those secrets to us.

Steps

Google moves buttons. The words below match Google’s IAM help. If a word is missing, stop and email a screenshot of the whole screen. Do not click a nearby button that only sounds similar.

Sign in as the Google account that owns the app. Open the IAM page.
At the top left, open the project picker. Select the app’s project. Copy the project ID (it looks like my-app-123456). You will paste it into the start form.
Click Grant access. In the principals box, paste exactly:

getappverified@gmail.com

Paste it. Do not retype it.
Click Select a role. Type OAuth Config Editor. Pick OAuth Config Editor. Do not pick Owner, the broad project Editor role, Viewer, or a role with “Legacy” in the name. Your own account can stay Owner or Editor. That is separate from the role you give us.
Click Save. If Google asks to send an invitation, say yes. “Pending” is normal until we accept it.

Easy mistakes

Wrong project. Check the name in the top bar before you save.
Picking Owner, or the broad Editor role, for our email “to be safe”. Your own account can stay Owner or Editor. Our email should be OAuth Config Editor.
A typo in the email. Paste getappverified@gmail.com.

Email us this

ADDED — Project ID: [the project id]
Role: OAuth Config Editor

Attach a screenshot of the IAM row that shows getappverified@gmail.com and the role. Pending is fine. Do not send a password.

When we are done

We will email you to remove us. The clicks are on the done-for-you page. You can remove us sooner any time. If you do that before we finish, the done-for-you refund exception applies.

If there is no Grant access button

You are probably signed in with an account that is not an owner of this project. Switch to the account that owns it. We will not ask you to hand that account’s password to us.

How Google describes granting a role: Grant, change, and revoke access.