> ## Documentation Index
> Fetch the complete documentation index at: https://help.scribe-mail.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Workspace API forbidden access

> Fix the Google Workspace API forbidden access error by turning on the Scribe add-in for the organizational unit or group your teammate belongs to.

When you see the message "Google Workspace API has forbidden access to this teammate's signature," Scribe is not allowed to install that teammate's signature. This happens when the Scribe [Google Workspace add-in](/en/integrations/signatures/google-workspace-client-side) is turned off for the organizational unit or group the teammate belongs to.

An administrator controls which users can access the add-in from the Google Workspace admin console. To let Scribe install the signature, turn the add-in on for that teammate's organizational unit or group, or for everyone.

<Warning>
  You need to be a Super Admin in your Google Workspace to change these settings. Invite someone from IT if you are not a Super Admin.
</Warning>

## Change who can access the add-in

<Steps>
  <Step title="Open the Google Workspace Marketplace apps">
    Open [your Google Workspace admin console](https://admin.google.com/), then go to Apps, Google Workspace Marketplace apps, and Apps list.
  </Step>

  <Step title="Open the Scribe app">
    Select Scribe in the list of installed Marketplace apps.

    <Frame>
      <img src="https://mintcdn.com/scribe/Z_G2D9X-Tlrxu_Eh/images/google-workspace-access-scribe-app-marketplace-list.png?fit=max&auto=format&n=Z_G2D9X-Tlrxu_Eh&q=85&s=df92501c460c74f2e41bac168a8a6b6c" alt="Google Workspace Marketplace apps list with the Scribe app entry" width="3456" height="1928" data-path="images/google-workspace-access-scribe-app-marketplace-list.png" />
    </Frame>
  </Step>

  <Step title="Open the User Access settings">
    In the User Access section, click "View organizational units and groups". This section also shows how many organizational units the add-in is currently turned on for.

    <Frame>
      <img src="https://mintcdn.com/scribe/Z_G2D9X-Tlrxu_Eh/images/google-workspace-access-grant-access-button.png?fit=max&auto=format&n=Z_G2D9X-Tlrxu_Eh&q=85&s=219a98dca04ac0e3002040b656b296db" alt="Scribe app configuration in the Google Workspace admin console showing the User Access section" width="3456" height="1926" data-path="images/google-workspace-access-grant-access-button.png" />
    </Frame>
  </Step>

  <Step title="Turn the add-in on for the right users">
    Select the organizational unit or group that includes the teammate whose signature failed to install, then set App distribution to On. To make the add-in available to your whole domain instead, choose On for everyone. Click Save.

    <Frame>
      <img src="https://mintcdn.com/scribe/r1lL8Wf_QXERzFxG/images/google-workspace-app-distribution-organizational-units.png?fit=max&auto=format&n=r1lL8Wf_QXERzFxG&q=85&s=e3ba7f58bbeae765f266eff43b9d0f2b" alt="Google Workspace app distribution settings with the organizational unit tree and the On for everyone option" width="3456" height="1928" data-path="images/google-workspace-app-distribution-organizational-units.png" />
    </Frame>
  </Step>

  <Step title="Reinstall the signature in Scribe">
    Back in Scribe, install the teammate's signature again. Once the add-in has access, the status changes from Failed to Installed.
  </Step>
</Steps>

<Note>
  Changes in the Google Workspace admin console can take a few minutes to apply. If the signature still fails right after you save, wait a few minutes and reinstall.
</Note>

## Related articles

* [Signature installation statuses and errors](/en/signature-installation-statuses-and-errors)
* [Google Workspace access lost](/en/troubleshooting/google-workspace-access-lost)
* [Google add-in not validating](/en/troubleshooting/google-add-in-not-validating)
* [Admin Policy Enforced](/en/troubleshooting/admin-policy-enforced)