My add on is developed for internal users. It can be accessed via Drive UI , editors access like Sheets, Docs and Slides. But whenever we are accessing the addon from Editors, for every file, we need to ask for the authorization as we don’t have File related information or runtime token. we are calling**requestFileScopeForActiveDocument** action. But I want to remove this step.
1 Like
Hi @Muppidathi_Hari You can’t remove the file authorization step if your add-on requests Drive/file scopes - it’s mandatory when accessing file data beyond the editor’s runtime token; the only way to avoid it is to remove broader Drive scopes and rely solely on the editor context.
the only way to avoid it is to remove broader Drive scopes and rely solely on the editor context. - what it means, my add on should be used for Mass Tagging from Drive UI and Single file Classification from Editor Context. Can you please reply as soon as possible