> For the complete documentation index, see [llms.txt](https://docs.aurinko.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurinko.io/faq/does-aurinko-provide-a-shared-verified-google-oauth-application.md).

# Does Aurinko provide a shared verified Google OAuth application?

Aurinko chooses not to provide a shared verified Google Cloud OAuth application at this time.

Instead, each customer configures and uses their own Google OAuth application. This approach aligns with Google's OAuth verification model, where the organization operating an application is responsible for managing its own OAuth credentials, verification process (when required), and compliance with Google's API policies.

Using a customer-owned OAuth application provides:

* Full ownership of the Google Cloud project and OAuth credentials.
* Independent management of Google's verification lifecycle.
* Control over security and compliance requirements.
* No dependency on a shared OAuth client managed by a third party.

Although configuring a Google OAuth application requires additional setup, it gives organizations full control over their Google integration and authentication infrastructure.

{% hint style="info" icon="file-lines" %}
See the [**Google OAuth Setup**](https://docs.aurinko.io/authentication/google-oauth-setup) guide for configuration instructions.
{% endhint %}

{% hint style="info" icon="file-lines" %}
To learn more about why Aurinko does not provide a shared Google OAuth application, read our blog post: [**The Hidden Risk of Using Shared OAuth Apps (Nylas, Unipile, etc.)**](https://dev.to/aspantel/the-hidden-risk-of-using-shared-oauth-apps-nylas-unipile-etc-3p5f).
{% endhint %}