> 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/resources/emails-and-notifications.md). # Emails & Notifications Boza sends operational updates by email, through the browser extension, and through the chat bot selected for your workspace's identity provider. ## Language and Sender Every email Boza sends is written in the **workspace language** chosen under **Settings → General → Language**, French or English, including the subject line, dates, and the footer. Change the language and the next email follows. By default, emails come from `Boza `. A workspace Admin can connect a Google Workspace or Microsoft 365 mailbox under **Settings → General → Email sending**; access-review invitations, reminders, and test reviews are then sent from that address, and the other emails keep the Boza address for now. See [Send Boza emails from your own mailbox](/docs/tutorials/send-emails-from-your-own-mailbox.md).
The access review invitation email in French, with the campaign name, the deadline, and the Vérifier mes accès button

The access review invitation, as a French workspace sends it.

## Manage Organization-Wide Notification Settings Open **Settings → Notifications**.
Settings Notifications page with Auto-renewal notifications and Ownership assignment notifications enabled

Each switch saves independently for the whole workspace.

Workspace administrators can change two settings: | Setting | When enabled | Recipients | | -------------------------------------- | ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | | **Auto-renewal notifications** | Includes automatically renewing subscriptions in the renewal-alert run | Workspace Admins, plus the application's Super Admin or Budget Owner when one is assigned | | **Ownership assignment notifications** | Sends a daily digest of new application-owner assignments | Each newly assigned owner | The switches default to enabled for a workspace that has not changed them. A success message confirms each saved change. {% hint style="info" %} These switches do not disable every email in Boza. They control only automatic-renewal alerts and ownership-assignment digests. {% endhint %} Turning off **Auto-renewal notifications** suppresses alerts for contracts marked as automatically renewing. Other renewal decision reminders can still be sent. ## Emails Boza Sends | Email | Trigger | Recipient | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | **Integration sync complete** | A connected application finishes synchronizing | The user associated with that sync | | **Renewal alert** | The daily alert run reaches a contract's pre-notice date, notice-period start, or renewal date | Workspace Admins, plus the application's Super Admin or Budget Owner when assigned | | **Shadow IT monthly summary** | On the first day of the month when newly discovered applications exist | Workspace Admins | | **Ownership assignment digest** | The daily digest finds new application-owner assignments and its setting is enabled | The newly assigned owners | | **Pennylane sync complete** | A Pennylane sync imports new invoices; the summary includes processed, duplicate, and failed counts | Workspace Admins | | **Invoices ready for review** | An invoice uploader clicks **Notify me when done** and the batch finishes | The uploader | | **Announcement** | A published [announcement](/docs/platform/announcements.md) includes **Email** | The resolved target audience | | **Access review invitation and reminder** | An access-review campaign launches (*Action needed — review your application access*); if reminders are enabled, one reminder per reviewer follows after the configured number of days while their review is still pending | The assigned reviewer | | **Test access review** | An admin sends a test review from **Access Review** | The chosen recipients | | **Integration connection lost** | A connected integration's authorization expires or is revoked; re-sent at most every three days while it stays disconnected | Workspace Admins | | **Capability map or data inventory ready** | A structure or population job you started finishes | The admin who started it | | **Admin welcome** | A user is promoted to workspace Admin | The new workspace Admin | | **Demo workspace ready** | A demo workspace is created | The demo admin | Every template exists in French and English and follows the workspace language. Announcement content is written by the announcement author and is sent as written. ## Invoice Processing Email **Notify me when done** is opt-in for each uploaded batch: 1. Upload invoices from **Subscriptions → Upload Invoices**. 2. While processing is active, click **Notify me when done**. 3. Boza confirms that the notification was registered and closes the processing dialog. 4. The uploader receives an email when the invoices are ready. See [Upload Invoices](/docs/inventory/subscriptions-and-vendors/upload-invoices.md) for duplicate and error handling. ## Chat Notifications The active chat platform follows the workspace identity provider: * **Google Workspace → Slack** * **Microsoft Entra ID → Microsoft Teams** Both chat paths are active, but the matching Boza bot must be deployed under **Integrations**. Workflow tasks such as onboarding, offboarding, access actions, and renewal actions use that provider-specific bot. Announcements can also use the same chat channel. See [Bot for Slack](/docs/integrations/bot-slack.md), [Bot for Microsoft Teams](/docs/integrations/bot-teams.md), and [Announcements](/docs/platform/announcements.md). ## Browser-Extension Notifications Announcements sent through **Browser Extension** appear to targeted extension users. This is the only announcement channel that can report **Read** and optional **Acknowledged** events. Email, Slack, and Teams report delivery status but do not provide browser-extension read or acknowledgment tracking. ## Troubleshooting * If a setting will not save, reload **Settings → Notifications** and try the switch again. * If Slack or Teams is disabled in the announcement composer, deploy the provider-appropriate bot from **Integrations**. * If an expected ownership digest is missing, confirm the setting is enabled and that the user was newly assigned an application ownership role. * If an invoice-ready email is missing, confirm that **Notify me when done** was selected for that batch. * If an announcement email is missing, check its target audience and the delivery statistics for a failed recipient. For help with a specific notification, contact ****. --- # 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/resources/emails-and-notifications.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.