I’m using an app script in my Google Sheet. It only does stuff inside the sheet. No Google Drive actions at all. But here’s the problem:
When I share the sheet and the other person tries to run the script, they get a message asking for Google Drive access. This doesn’t make sense because the script doesn’t touch their Drive.
I’m wondering if there’s a trick to stop this permission pop-up. It seems unnecessary and might freak out the people I’m sharing with. They might think the script is doing more than it really is.
Has anyone found a way around this? Or is it just how Google scripts work? Any tips would be great!
I encountered a similar issue and eventually discovered that explicitly defining the OAuth scopes in the manifest file helped greatly. By enabling the manifest view in the script editor and then editing the file to include only the scope for the current spreadsheet—namely, “https://www.googleapis.com/auth/spreadsheets.currentonly”—the authorization process became much smoother. This approach limits the permissions to those absolutely necessary, preventing unnecessary prompts for additional access. Although it may sound technical, this method proved effective and is worth trying.
hey, i’ve been there too. try deploying the script as a web app so you control the permissions, reducing scary popups. go to publish > deploy as web app in the script editor. works for me!
I’ve dealt with this issue before, and there’s a workaround that might help. Try explicitly defining the OAuth scopes in your script’s manifest file. It’s a bit technical, but not too difficult. Here’s what you do:
This limits permissions to just the current spreadsheet. It should reduce those annoying authorization prompts for your users. It’s not a perfect solution, but it’s made a big difference in my projects. Give it a shot and see if it helps!