Support with Google Cloud Platform (GCP) App Verification Process and to use Nylas shared GCP

Question and Answers
1

Hi Team,

We are experiencing delay with the Google Cloud Platform (GCP) App Verification process. It appears that leveraging the Nylas Shared GCP project could help us move forward.

I would appreciate it if someone from your team could reach out to me with more information, so we can implement this solution as soon as possible.

Thank you,

2

Hey @Malcolm , appreciate you reaching out. Will get someone to reach out today about the Shared GCP Project today!

3

Hi @Malcolm , John from our team has reached out to you - please let me know if you have any issues with booking some time with him.

4

Thankyou @nick.barraclough . John did reach out to me, but I have two concerns:

  1. I contacted the Nylas support team, and they completely denied that Nylas offers a shared GCP. However, your team has stated otherwise—could you please clarify?

  2. Would it be possible to schedule a meeting with John sooner, ideally today? We’re aiming to launch our app on Monday, so time is quite critical.

5

Hey @Malcolm ,

  1. This was just some confusion about responsibilities that we’ve cleared up between the teams. Our support team has a technical focus & the large volume of their tickets are supporting our customer’s implementations - but I appreciate you bringing this up. Always room for improvement!
  2. John’s reaching out & has some time free today - keep an eye out for his email!
6

@nick.barraclough Thankyou we recently purchased the Nylas add-on for the shared GCP project. While we appreciate the functionality, we’ve noticed that the OAuth consent screen is
displaying Nylas branding.

Given the significant cost of the add-on, we were expecting that the
authentication flow would reflect our own platform’s branding rather
than Nylas’. The presence of third-party branding in a user-facing
flow can be confusing for our users and doesn’t align with our brand
experience.

Could you please advise on how we can replace the Nylas branding with
our own on the OAuth consent screen?

7

Hello @Malcolm ,

Thanks for reaching out about customizing the OAuth consent screen branding.

If showing your own branding is important, the Nylas Shared GCP project works well as an interim solution while your app is being verified — that’s where you’ll have full control over your branding. Unfortunately, we can’t remove Nylas branding from the shared GCP app, as it’s tied to Nylas’ verified OAuth configuration. I’ve shared more details on why below.

About the Shared GCP Project

When you use the Nylas Shared GCP project, you’re leveraging Nylas’ verified Google OAuth app. This helps you get to market faster, but the consent screen will always display Nylas branding (app name, publisher, and policy links), which can’t be customized since it comes directly from Google’s configuration.

To Show Your Own Branding

To display your company’s branding on the Google OAuth consent screen, you’ll need to:

  • Create your own Google Cloud Project and OAuth app

  • Configure your consent screen with your company details

  • Complete Google’s verification and security assessment (if required)

  • Update your Nylas connector to use your credentials instead of the shared project

Once your app is verified, the consent screen will reflect your company’s branding.

I hope this helps, please let us know if you have any questions!