> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/getting-started/document-editor-installation/google-workspace.md).

# Google Workspace

Protege Review’s Google Workspace plugin integrates directly with Google Docs and Slides, allowing marketing and legal teams to review content for legal and compliance risks without leaving their documents.<br>

In addition to the plugin, we offer a Chrome Extension that unlocks advanced features like in-line commenting for deeper collaboration. To use the plugin, you’ll need a Google Workspace account.

#### 🔧 Browser Compatibility

Protege is tested and fully compatible with Google Chrome and Brave browsers.

## **Part 1.** Installing the Google Workspace Plugin

You can install the plugin in two ways:

* IT Admin Installation – for organization-wide deployment.
* Individual User Installation – for single machine install.

####

{% tabs %}
{% tab title="Individual Installation" %}

1. **Access Google Workspace Marketplace**: Log in to your Google Workspace account.
2. **Navigate to Marketplace**: Visit the listing for [Protege for Google Workspace Marketplace](https://workspace.google.com/marketplace/app/protege_ai/72543460431)
3. **Install the Plugin**: On the Protege Plugin listing, select "Individual Install." Follow the on-screen instructions to complete the installation.

   <figure><img src="https://2804394160-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD9Htw9DUg294GuYmAyyj%2Fuploads%2Fgit-blob-9e3c233202dbef347df854cbba54477d5b15fed6%2FScreenshot%202024-02-27%20at%208.20.01%E2%80%AFPM.png?alt=media" alt=""><figcaption></figcaption></figure>
4. **Grant Permissions**: Grant the necessary permissions to the plugin when prompted.
5. **Complete Installation**: Once installed, the plugin will be accessible within your Google Workspace (Docs and Slides).
6. **Test the Plug-In:** Open a new Google Document and enter the text you want reviewed. Navigate to the Extensions tab, select "Protege Review", and then select "Open".

   <figure><img src="https://2804394160-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD9Htw9DUg294GuYmAyyj%2Fuploads%2Fgit-blob-0ce3c74adadc12012259ebe39d2d65e7665725cb%2FScreenshot%202024-02-27%20at%208.22.35%E2%80%AFPM.png?alt=media" alt=""><figcaption></figcaption></figure>

{% endtab %}

{% tab title="IT Admin Installation" %}

1. **Admin Console Access**: As an IT Admin, log in to your Google Workspace Admin Console.
2. **Navigate to Marketplace**: Visit the listing for [Protege for Google Workspace Marketplace](https://workspace.google.com/marketplace/app/protege_ai/521295007931)
3. **Install the Plugin**: On the Protege Plugin listing, select "Admin Install." Follow the on-screen instructions to complete the installation.

   <figure><img src="https://2804394160-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD9Htw9DUg294GuYmAyyj%2Fuploads%2Fgit-blob-9e3c233202dbef347df854cbba54477d5b15fed6%2FScreenshot%202024-02-27%20at%208.20.01%E2%80%AFPM.png?alt=media" alt=""><figcaption></figcaption></figure>
4. **Review Permissions**: Review the permissions required by the plugin and confirm the installation.
5. **Deployment Settings**: Configure deployment settings as per your organization's requirements. You may choose to deploy the plugin to all users or specific organizational units.
6. **Complete Installation**: Once configured, complete the installation process. The plugin will now be available to all users within your organization.
   {% endtab %}
   {% endtabs %}

## Part 2. Chrome Extension Installation

1. **Navigate to Marketplace**: Visit the listing for [Protege for Google Chrome](https://chromewebstore.google.com/detail/protege-ai/pknoakkhmfneejkpnjfgkcnphpjhjcmf)
2. **Install the Chrome Extension**: On the Protege Plugin listing, select "Add to Chrome" Follow the on-screen instructions to complete the installation.

<figure><img src="https://2804394160-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD9Htw9DUg294GuYmAyyj%2Fuploads%2Fgit-blob-0a1c4511c64653476f48de0aa7fbbb4c403248ad%2FScreenshot%202025-04-24%20at%2008.29.29PM.png?alt=media" alt=""><figcaption></figcaption></figure>

####

#### Note:

* If you encounter any issues during the installation process or require assistance, please reach out to our support team at <support@tryprotege.com>. We're here to help ensure a smooth installation and seamless integration with your workflow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tryprotege.com/review/getting-started/document-editor-installation/google-workspace.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.