> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/more-features/expel-managed-phishing/setup-guides/expel-managed-phishing-extension-for-chrome.md).

# Expel Managed Phishing Extension for Chrome

## Prerequisites

* You must be one of your organization's Google Workspace administrators with the proper permissions.

## Install the Extension

1. Log in to the [Google Workspace admin console](https://admin.google.com/).
2. Navigate to **Devices > Chrome > Apps & extensions > Users & browsers**.
3. In the bottom right, select the **plus (+)** icon in the yellow circle and select **Add Chrome app or extension by ID**.

<div align="left"><figure><img src="/files/2f8FSQp2kds1U6j4PQVi" alt="An image of the list of icons, showing which one to choose." width="246"><figcaption></figcaption></figure></div>

4. Enter the value `gpkcimdiphdhnenbncknfiakplflhmnc` and then select **SAVE**.
5. Navigate back to the [Google Workspace admin console](https://admin.google.com/) and select **Security**.
6. Scroll down and open **API controls**.
7. Select **MANAGE THIRD-PARTY APP ACCESS**.
8. In the section Connected apps, hover over **Expel for Phishing** and select **Change access**.
9. Choose **Trusted: Can access all Google services** and then select **SAVE**. The Expel Managed Phishing app is now listed as Trusted in the Connected apps view.

<div align="left"><figure><img src="/files/A47SaDX0HLat7Df8Rtiy" alt="An image showing the trusted access." width="563"><figcaption></figcaption></figure></div>

10. Go back to the Admin console and select **Security**.
11. Scroll down and open **API controls**.
12. Select **MANAGE DOMAIN WIDE DELEGATION**.
13. Select **Add new**.
14. Enter the following for the **Client ID** and the **OAuth Scopes**:
    * **Client ID** - `528472867238-v8803num13j6691ue52qqm6tuoqpu9ns.apps.googleusercontent.com`
    * **OAuth scopes** - `https://www.googleapis.com/auth/gmail.modify`
15. Select **Authorize**.

## Update the Extension

1. Log in to the [Google Workspace admin console](https://admin.google.com/).
2. Navigate to **Devices > Chrome > Apps & extensions > Users & browsers**.
3. Find the **Expel Managed Phishing** extension and select the row.

<div align="left"><figure><img src="/files/4dSDzkEP3K80vOXvqtIO" alt="Image of the row where you can install." width="506"><figcaption></figcaption></figure></div>

4. In the panel that opens, copy the **JSON value** under **Policy for extensions** and paste it into a text editor for use in a later step.

<div align="left"><figure><img src="/files/VpcjMfo3zGZSzqbN2uHR" alt="Image highlighting the policy section." width="563"><figcaption></figcaption></figure></div>

5. Select the trash can icon to delete the extension.
6. Select **SAVE** to complete the deletion process.
7. In the bottom right, select the **plus (+)** icon in the yellow circle and select **Add Chrome app or extension by ID**.

<div align="left"><figure><img src="/files/2f8FSQp2kds1U6j4PQVi" alt="An image of the list of icons, showing which one to choose." width="246"><figcaption></figcaption></figure></div>

8. Enter the value `gpkcimdiphdhnenbncknfiakplflhmnc` and then select **SAVE**. A panel opens.
9. In the **Policy for extensions** field, paste in the **JSON value** you copied.
10. Select **SAVE**.
11. Navigate back to the [Google Workspace admin console](https://admin.google.com/) and select **Security**.
12. Scroll down and open **API controls**.
13. Select **MANAGE THIRD-PARTY APP ACCESS**.
14. In the section Connected apps, hover over **Expel for Phishing** and select **Change access**.
15. Choose **Trusted: Can access all Google services** and then select **SAVE**. The Expel Managed Phishing app is now listed as Trusted in the Connected apps view.

<div align="left"><figure><img src="/files/A47SaDX0HLat7Df8Rtiy" alt="An image showing the trusted access." width="563"><figcaption></figcaption></figure></div>

16. Go back to the Admin console and select **Security**.
17. Scroll down and open **API controls**.
18. Select **MANAGE DOMAIN WIDE DELEGATION**.
19. Select **Add new**.
20. Enter the following for the **Client ID** and the **OAuth Scopes**:
    * **Client ID** - `528472867238-v8803num13j6691ue52qqm6tuoqpu9ns.apps.googleusercontent.com`
    * **OAuth scopes** - `https://www.googleapis.com/auth/gmail.modify`
21. Select **Authorize**.
22. To confirm the update was successful, open a Chrome browser and go to [chrome://extensions](chrome://extensions/).
23. Select the toggle to **enable Developer mode**.

<div align="left"><figure><img src="/files/483pb1t1ocOcJqASrcAt" alt="An image showing the developer mode toggle." width="563"><figcaption></figcaption></figure></div>

24. Validate that the version of Expel Managed Phishing installed is at least version `0.0.19`.

<div align="left"><figure><img src="/files/sqYPqeyInfpLY7mFGKi8" alt="An image showing the correct version." width="293"><figcaption></figcaption></figure></div>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.expel.io/more-features/expel-managed-phishing/setup-guides/expel-managed-phishing-extension-for-chrome.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
