Users must [authorize](https://developers.google.com/apps-script/guides/client-verification) your [[Google Apps Script]] project if it accesses the users' private data or launches a sidebar or modal dialog box. User from within your own organization will need to select the account to grant access to and will then see a dialog box that describes what the script will be allowed to do. Users from outside of your organization will see a warning that Google hasn't verified the app and will need to click a small Advanced button, click a link marked "Unsafe" and then allow access. You can request verification if you plan to share the app widely, however. In user testing, I've found that most users will not authorize Google Apps Script. It's just too scary and they don't understand the benefits (whether verified or not). Keep this in mind before developing a project that will require users to authorize Google Apps Script. > [!Tip] > You can learn more about unverified apps and request Google review your app so that users outside your organization don't see the unverified app screen [here](https://support.google.com/cloud/answer/7454865). Apps deployed within your own organization don't need to go through verification. > [!tip]- Additional Resources > - [Google Apps Script Authorization Guide](https://developers.google.com/apps-script/guides/services/authorization)