> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/tutorials/send-emails-from-your-own-mailbox.md).

# Send Boza Emails from Your Own Mailbox

Have access-review invitations and reminders reach your employees from an address on your own domain instead of the generic Boza address, so fewer of them are ignored or reported as phishing.

## Before you start

* You are a workspace **Admin**.
* You can sign in to a Google Workspace or Microsoft 365 mailbox that should become the sender, for example `it@example.com`. A shared mailbox or a dedicated no-reply address works well.
* Boza only needs permission to **send**. It never reads that mailbox.

## Steps

1. Open **Settings → General** and scroll to **Email sending**. The preview shows how your employees see Boza's emails today: with the default setting, they come from `Boza <notifications@getboza.io>`.

<figure><img src="https://1674559363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvSdGShklbloRzyUwwMzX%2Fuploads%2Fgit-blob-685dbfc51f2216cec9b2c1f8cab0bc844c237c94%2Fboza-settings-general-language-email.png?alt=media" alt="Settings General page showing the Language selector and the Email sending section with the default sender preview and Connect buttons for Gmail and Microsoft Outlook"><figcaption></figcaption></figure>

2. Click **Connect** next to **Gmail** or **Microsoft Outlook**. Boza opens the **Integrations** page on that connector.

<figure><img src="https://1674559363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvSdGShklbloRzyUwwMzX%2Fuploads%2Fgit-blob-d8fae51c69d23219263ce240c5efff2f2b03d16a%2Fboza-integrations-gmail-connect.png?alt=media" alt="Integrations page filtered on Gmail, ready to connect"><figcaption></figcaption></figure>

3. Click **Connect** on the connector and sign in with the mailbox that should send the emails. Approve the send-only permission when Google or Microsoft asks for it.
4. Return to **Settings → General**. The provider now shows **Connected** and **Sending as** the address you signed in with, and the preview updates.

## Expected result

From the next access-review email onwards, invitations, reminders, and test reviews show your address as the sender. They are written in your workspace language, which you change with the **Language** setting just above.

{% hint style="info" %}
Renewal alerts and the other notifications still come from `notifications@getboza.io` for now.
{% endhint %}

## Troubleshooting

* **Connection lost.** The authorization expired or was revoked; the provider row says so. Click **Manage**, reconnect with the same mailbox, and the status clears. Until then Boza falls back to the default address, so no email is lost.
* **Connect is greyed out on one provider.** A workspace sends from one mailbox at a time. Disconnect the other provider from **Integrations** first.
* **Employees still see the Boza address.** Check that the connection succeeded in **Integrations**, then send yourself a test access review from **Access review → Configure** to confirm.

## Related guides

* [Settings](/docs/settings-and-security/settings.md#email-sending)
* [Emails and notifications](/docs/resources/emails-and-notifications.md)
* [Run your first access review](/docs/tutorials/run-your-first-access-review.md)


---

# 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://boza.gitbook.io/docs/tutorials/send-emails-from-your-own-mailbox.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.