# Solution for Google Verification for Packs

**URL:** <https://connect.superhuman.com/t/solution-for-google-verification-for-packs/34023>\
**Category:** Making Packs\
**Created:** [September 23, 2022, 10:05pm UTC](https://connect.superhuman.com/t/solution-for-google-verification-for-packs/34023 "2022-09-23T22:05:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eric\_Koleda](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/eric_koleda/32/50286_2.png) [@Eric\_Koleda](https://connect.superhuman.com/u/Eric_Koleda)\
**Post date:** [September 23, 2022, 10:05pm UTC](https://connect.superhuman.com/t/solution-for-google-verification-for-packs/34023/1 "2022-09-23T22:05:40Z")

</div>

Hello Pack makers - As you may have known, there were some issues that made it impossible to complete Google’s OAuth verification process for a Coda Pack. This meant that Packs that used OAuth to access user data had a scary approval prompt and were capped at 100 users.

I’m happy to announce that we’ve found a policy workaround that allows Coda Packs to be verified! It’s a bit of a long story, but you can read more about it in our FAQ:

> **[Frequently asked questions - Coda Pack SDK](https://coda.io/packs/build/latest/guides/faq/#google)**
>
> Answers to some of the most common questions about building Packs.

I’ve successfully applied this workaround to one of my personal Packs, as has another member of the community. If you were holding off on creating or publishing a Pack due to this issue, you are now free to explore the Google-verse of Packs!
