> For the complete documentation index, see [llms.txt](https://support.suptask.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.suptask.com/integrations-automations-and-workflows/email-ticketing-setup/how-to-configure-the-email-integration-for-gmail-and-google-workspaces.md).

# Gmail & Google Workspaces

### Overview

In this article we help guide you through how a common setup can look in Gmail & Google Workspaces when integrated with Suptask. 

The Suptask Email integration is receiving emails from an address which in turn forwards the emails to Suptask. By using forwarding from a local address on the customer side, Suptask can validate the emails and direct them to the correct Inbox, as well as secure who delivers the emails to Suptask.

[Learn more on how the email integration works.](https://support.suptask.com/en/getting-started/how-to-set-up-the-email-integration)

We will make use of the **Routing rules** **in Gmail** in order to setup forwarding to Suptask. 

***

### How to configure forwarding 

Navigate to the Gmail app configuration inside of the Admin panel of Google Workspaces. In here you can set

1. In the Workspace Admin panel, open the **Apps**
2. Select **Google Workspace**
3. Select the **Gmail app**
4. Select **Default routing**
5. Select **Add Another Rule** in order to create a new routing rule.

The important fields to set up next in the rule are: 

* **Single recipient Email address** - Which incoming email this rule should be applied to. This is your local address. 
* **Add more recipients** - Use the Basic setup and enter the Suptask email address to forward emails to: **<incoming@suptask-mail.com>**
* **Options** - Make sure to have this value selected: **Perform this action on non-recognized and recognized addresses**

***

### Example of a routing rules

<figure><img src="/files/3icmj6NOIYArxCcqcUnV" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/3pe5FSxHwEGAYzl3Jb3D" alt="" width="375"><figcaption></figcaption></figure>