> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/email-notifications.md). # Notifications and Reminders ### Overview Notifications inform reviewers and other stakeholders of important events, such as when a review starts, re-assignments occur, and deadlines pass. These notifications can be delivered via email, Slack, or both. Veza includes three types of notifications, which an administrator can customize with templates. * **Notifications**: Event-based, sent when a review starts or finishes, or on row reassignment. * **Reminders**: Time-based, sent around the deadline or period of activity when there is remaining work. * **Final Reminders**: Similar to reminders, highlighting missed deadlines or extended periods of inactivity. ### Delivery Methods Access Review notifications can be delivered through multiple channels: * **Email**: Traditional email notifications sent to reviewers, managers, and additional recipients (default) * **Slack App**: Direct message notifications sent to individual reviewers via the Veza Slackbot You can enable one or both delivery methods based on your team's preferences. When both are enabled, reviewers receive notifications through both channels simultaneously. #### Prerequisites for Slack App Notifications To enable Slack App notifications: 1. Configure the Slack App integration (see [Slack App Notifications](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/slack-app.md)) 2. The feature flag `UI_SLACK_APP_INTEGRATION` must be enabled for your organization (contact Veza support) 3. Users must exist in both Veza and Slack with matching email addresses #### Configuring Delivery Methods When creating or editing an Access Review configuration: 1. Navigate to the **Notification Settings** section 2. Under **Delivery options**, select: * **Email**: Send notifications via email * **Slack App**: Send direct messages to reviewers via Slackbot 3. If Slack App is enabled, choose your configured Slack App from the dropdown 4. Select which events trigger notifications: * Review started * Review completed * Reviewer changed * Reminder notifications * Escalation notifications All configured notification events will be delivered as direct messages to assigned reviewers through the selected delivery methods. {% hint style="info" %} **For team channel notifications**: Use Slack webhooks in the **Veza Actions** section to post decision events (approve/reject/complete) to team channels. See [Slack Webhook Integration](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/slack.md). Both direct messages and channel notifications can be used simultaneously. {% endhint %} #### First-Time User Experience When reviewers receive their first Slack notification: 1. If they haven't connected their Slack account to Veza, the message includes a "Connect" button 2. Clicking "Connect" redirects them to Veza's login page 3. After authentication, their Slack and Veza accounts are linked 4. Subsequent notifications include interactive "View", "Approve", and "Deny" buttons Operators assign default notification settings when creating a configuration. Reviews created for the configuration will inherit these settings. Operators can later customize notification settings for specific reviews. For multi-user access reviews, you will typically want to fine-tune reminders to meet your requirements, for example: * Reviewers and review owners, informing them when rows are re-assigned. * Reviewers and their managers, if users are inactive when further action is required. * External stakeholders, on review completion or after a deadline passes. This document describes notification options for Veza Access Reviews, and how to edit notifications for a configuration or a review. {% hint style="info" %} Administrators can configure global notification exclusions to prevent specific reviews from sending digest notifications or alerts based on labels. See [Configure Notification Exclusions](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/configure-notification-exclusions.md). {% endhint %} ### Configuring notifications & reminders You can add reminders when creating a configuration by enabling them in the **Notifications** section of the configuration builder. To enable notifications, specify the recipients and the conditions that will result in an email. **Recipients** can be: * **Reviewers**: Users assigned to rows in the review, including default reviewers and any reassigned reviewers. * **Reviewer Managers**: Users identified by Veza as the manager of an assigned reviewer, possible after enabling a global identity provider for Veza Access Reviews. * **Additional Recipients**: Any other stakeholders, provided as a comma-separated list of emails. You can use this option to inform external users about completion status, deadlines, and delays. **Notifications** can trigger: * **On review start**: Upon review creation or after publishing a draft review. Use this option to inform reviewers who are auto-assigned on review creation. * **On row reassignment**: After a reviewer is assigned to a row by a user operation (API or GUI-initiated). It does not include reviewers assigned at review creation. * **On review completion**: When the review is marked "Complete". **Reminders** can trigger: * **Every (number of days) if no changes by reviewers in (number of days)**: Periodic reminders when reviewers have not acted on their assigned rows. * **On (number of days) before review due date**: Sent based on an upcoming due date. * **On due date**: Sent when the review is due. * **(Number of days) after due date**: Sent when the review deadline has passed. **Final Reminders** have the same triggers and use the same template as “Action Needed” reminders. Use them to add escalated reminders, emphasizing missed deadlines or extended periods of inactivity. For example, a reminder might notify the reviewer after a few days of no activity, and a final reminder might notify both the reviewer and their manager if there have been no changes in a week. {% hint style="info" %} Reminders and final reminders are sent at 11 AM PST on the specified date. {% endhint %} ### Reassignment Needed notifications Veza can automatically detect when an assigned reviewer's account has been deactivated or removed and notify the appropriate parties so that rows can be reassigned before the review expires. {% hint style="info" %} **Prerequisite**: Reassignment Needed notifications require a [Global Identity Provider](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/global-idp-settings.md) to be configured. When a global IdP is configured, the **Reassignment Needed** section appears in the review configuration's notification settings. {% endhint %} When enabled, Veza runs a background check approximately every 24 hours while the review is in progress. It compares the current list of assigned reviewers against the integrated IdP and flags any reviewer whose account: * Has `is_active = false` in the IdP, or * No longer exists in the IdP (deleted or deprovisioned) When inactive reviewers are detected, notification emails are sent to the configured recipients. {% hint style="info" %} Unlike other notification types, **Reviewers** is not a recipient option for Reassignment Needed notifications. Only **Reviewer Managers** and **Additional Recipients** are available, so that notifications reach someone with authority to reassign the affected rows. {% endhint %} **To enable Reassignment Needed notifications:** 1. Go to **Access Reviews** > **Configurations** and open a configuration. 2. Click **Edit** and scroll to the **Advanced Notifications** section. 3. Under **Reassignment Needed**, check **Reviewer account has been detected as inactive**. 4. Select recipients: * **Reviewer Managers**: Notifies the manager of each inactive reviewer. Veza sends a separate email to each manager listing only their direct report's affected rows. * **Additional Recipients**: Sends a single email listing all inactive reviewers across the review. 5. **Save** your changes. ### Edit notifications and reminders for a configuration Saving changes to email notifications at the configuration level causes both active reviews and new reviews for that configuration to use the updated settings. To change the default email notifications for an existing configuration: 1. Go to **Access Reviews** > **Configurations**. 2. Click the configuration name to view details. 3. On the **Configuration Details** page, click **Edit**. 4. Scroll down to the **Advanced Notifications** section. 5. Configure notification settings using the checkboxes to enable recipients and triggers: * **Review Notifications**: * Under **When**, select events that trigger notifications (Review has been started, Review has been completed, Review row has been reassigned) * Under **Notify**, select recipients (Reviewers, Managers, Additional Recipients) * **Reviewer Notifications**: * Under **When**, select timing conditions (Review is due, days before a review is due, days after a review is due, or reminders when no changes have been made) * Under **Notify**, select recipients (Reviewers, Managers, Additional Recipients) 6. **Save** your changes. ### Edit notifications and reminders for a review Operators and administrators can customize notifications for individual reviews. These settings appear in the reviewer's interface on the review details sidebar. To edit email notifications for an in-progress review: 1. Go to **Access Reviews** > **Reviews**, or open the review from the **Configuration Details** page. 2. Click on the review's name to open the reviewer's interface. 3. On the **Review Details** sidebar, find **Notifications and Reminders** and click **Open**. ![Open notification settings or edit Veza Actions.](/files/a5T88w56krkUoiGASfWZ) 4. Use the **Edit Configuration Notifications & Reminders** form to add recipients and triggers. 5. Click **Save** when finished. ### Customizing notification content To customize the email content, subject lines, and branding for Access Review notifications, see [Notification Templates](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/email-templates.md) in the Administration section. ### See also * [Notifications Overview](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications.md) - Notification system concepts and delivery channels * [Notification Templates](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/email-templates.md) - Customize notification content and branding * [Delivery Settings](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/delivery-settings.md) - Configure digest schedules and recipient controls * [Create a Configuration](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/review-configuration.md) * [Veza Actions for Access Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/veza-actions.md) * [Notification Templates API](/4yItIzMvkpAvMVFAamTf/developers/api/notification-templates.md) * [Notifications API Reference](/4yItIzMvkpAvMVFAamTf/developers/api/notification-templates/email-templates-api.md) * [Entity Owners and Resource Manager Tags](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/managers-and-resource-owners.md) * [Reviewer Digest Notifications](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/digest-notifications.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/email-notifications.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.