> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/request-management/request-and-service-management-email/forward-emails.md). # Forward Gmail emails to Siit Find your team Siit email address in Channel settings and set up Gmail forwarding from a shared inbox so incoming emails become Siit requests, including Google verification **Where to find my team's Siit e-mail address?** You can find the Siit e-mail addresses of all the teams in the Channel section of Settings. It always has the format `@.siit-mail.com`, e.g. , where `office` is the team slug and `acme` is the organization slug.

ℹ️ *You have a **shared inbox** setup if you and your colleagues share access to the same e-mail inbox.* * Log in to your shared e-mail inbox * Go to [**Settings**](https://mail.google.com/mail/u/0/#settings/fwdandpop) → **Forwarding and POP/IMAP** * Click on **Add a forwarding address** and enter the address of your team in Siit e.g. * Confirm the forwarding in the next dialog

Google needs to verify that the e-mail address you're forwarding to is really owned by you. To do so they send a verification code to the e-mail address which you need to enter. * Once you add the forwarding e-mail go to Siit to find a new request from Google with title containing **Forwarding Confirmation.** * You need to contact our support team or your point of contact to provide you the **digit code.** * Either copy the **9 digit code** or **click on the first link in the e-mail** to confirm the forwarding. Once confirmed you can then **enable forwarding** by going to **Gmail → Settings → Forwarding and POP/IMAP** and then selecting **"Forward a copy of incoming mail to…"** and selecting the address you just added (in most cases it will be pre-selected). You can also choose what to do with the forwarded e-mail (keep in Inbox, Archive, or Delete). --- # 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.siit.io/guides/request-management/request-and-service-management-email/forward-emails.md?ask=&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.