How to approach rebranding in verified OAuth screen?

[VojtechOram]

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.

[Willbin]

Hello @VojtechOram,

Welcome to Google Cloud Community!

This document might be useful for you. Please also note that:

---

If you change any of the details that appear on your OAuth consent screen, such as the app's logo, name, home page, privacy policy URI, or authorized domains, you need to resubmit the new branding configuration for verification, and receive approval, before the updates take effect on your OAuth consent screen.

---

Thanks!

[VojtechOram]

Thanks for answering, but it did not really answered my questions. I guess I can just do a changes to OAuth screen and it will be unchanged for clients in meantime before changes will be approved. But I still don't know if I should change the branding of app before the OAuth screen changes, in the process of changing or after. 

[VojtechOram · Accepted solution]

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.

[tirathsharma71]

@VojtechOram 
Can you please tell in test server you have different subdomain, So you added same or your production server url on clould branding section.

[VojtechOram]

Yes, we had different subdomain on test server. And on the cloud branding section, we put the production URL