This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

How to approach rebranding in verified OAuth screen?

Posted on 07-13-2023 06:44 AM
VojtechOram
Bronze 1
Bronze 1
Reply posted on --/--/---- --:-- AM

We have a verified OAuth consent screen with some sensitive and restricted scopes (tier 2). But we are considering rebranding, which will mean changing app name, app domain and logo. How to approach this? The app is used in production so we don't want to loose the verification in the meantime before the change is approved. We will also be changing the name in the app on every places where it is being used - should we change it before or after we change it in OAuth consent screen as Google console?
I did go through FAQ but did not found the answer to this.

Solved Solved
1 5 1,445
Jump to Solution
1 ACCEPTED SOLUTION

Posted on --/--/---- --:-- AM
VojtechOram
Bronze 1
Bronze 1
Reply posted on --/--/---- --:-- AM

How we did it in the end? Deployed the the brand change on test server, where we shoot the video for verification. Than submitted the change of branding at Google console with the video, changed URLs and other things to new branding. After the verification was successfully done, we deployed the branding change to production server. 
It took 3 working days and no problems found. Which could of course vary.

View solution in original post

Jump to Solution
5 REPLIES 5
Top Labels in this Space
Top Solution Authors
View all