Admin Setup Guide (Organization-wide Deployment)

If your organization's security settings leave the OAuth scopes TateGaki needs (Google Drive drive.file, email address userinfo.email, etc.) unapproved or untrusted, users cannot consent and hit access / drive.files.insert permission errors.

How to check and fix

1. Sign in to admin.google.com with an administrator account.
2. Go to Security > Access and data control > API controls.
3. Under Manage third-party app access (third-party apps / Google Workspace Marketplace apps), find TateGaki. If it isn't listed, choose "Add app" and select TateGaki from Marketplace apps.
4. Set TateGaki to "Trusted" and approve access to the requested scopes such as Drive (drive.file) and email address (userinfo.email).
5. Confirm the setting applies to the target organizational unit (OU).

Note: changes can take time to propagate. Afterward, ask users to reload the browser and reopen the add-on.

When installing from Marketplace organization-wide, if distribution is limited to only certain OUs or groups, users outside that scope cannot use the app and get access errors.

How to check and fix

1. Sign in to admin.google.com with an administrator account.
2. Go to Apps > Google Workspace Marketplace apps > Apps list.
3. Select TateGaki from the list.
4. In the Distribution (who can use) setting, turn the app ON (available) for the target OU or group. For company-wide use, turn it on for the top-level organization.
5. If needed, also check your Marketplace allowlist settings so individual users are allowed to install.

Note: propagation can take from tens of minutes to a few hours. Wait a while, then ask affected users to try again.

This symptom occurs even when the administrator-side settings (User Access / Data Access) are correct. Please ask the user to try the steps below first.

Symptom: The add-on opens, but "Import from Docs", "Export to Docs", and "Save to Drive" fail with Authorization is required to perform that action. The add-on itself may also fail to start.

Cause: When several Google accounts are signed in at the same time, the account running the add-on can differ from the account that granted permission. This is how Google handles multiple sessions and cannot be worked around by the add-on.

What to ask the user to do (any one of these resolves it)

1. Open the document in an Incognito window, signed in with only the account they use.
2. Make that account their default account (the first one they sign in with).
3. Use a separate Chrome profile for each account.

Note: This symptom cannot be resolved by changing organization settings. It requires isolating the user's sign-in state.