# Veza Actions Veza Actions enable notifications to external systems and email recipients when events occur across the platform. The notification system supports multiple delivery channels and customizable email templates, enabling organizations to tailor communications to their workflows. ## Notification types Veza sends notifications for events across several product areas: | Product Area | Events | Learn More | | ------------------------ | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | **Access Reviews** | Review started, completed, reassigned; reminders; digest summaries; row decisions | [Notifications and Reminders](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/email-notifications.md) | | **Lifecycle Management** | Identity created, synced, deleted; relationships changed; password events; workflow failures | [LCM notifications](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/lifecycle-management-notification-templates.md) | | **Access Intelligence** | Rule-triggered alerts; risk notifications from saved queries; remediation actions for risk findings | [Rules and Alerts](/4yItIzMvkpAvMVFAamTf/features/insights/rules-and-alerts.md), [Risks](/4yItIzMvkpAvMVFAamTf/features/insights/risks.md) | | **Access Requests** | Request created, state changed, approver assigned, completed, failed | [Access Hub](/4yItIzMvkpAvMVFAamTf/features/access-hub.md) | ## Delivery channels Veza supports multiple channels for delivering notifications: ### Email Email is the default notification method for Access Reviews, Lifecycle Management, and Rules and Alerts. Veza sends emails from `noreply@veza.com` by default, or from a custom domain if custom SMTP is configured. See [Email Notifications](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/email.md) for setup and SMTP configuration, and [Notification Templates](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/email-templates.md) for content customization. ### External systems Veza Actions enable notifications to external systems for alerting and remediation workflows: * [Microsoft Teams](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/teams.md): Channel notifications via webhooks * [Jira](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md): Automatic ticket creation for alerts and rejected access * [ServiceNow](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/servicenow.md): Incident and change management integration * [Slack App](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/slack-app.md): Direct messages to individual reviewers via the Veza Slackbot * [Slack Webhook](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/slack.md): Channel notifications for team updates (via Veza Actions) * [Custom Webhooks](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/webhooks.md): Generic HTTP endpoints for custom integrations See [Delivery Destinations](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations.md) for configuration guides. ## Configuring Veza Actions Administrators configure Veza Actions on the **Integrations** > *Veza Actions* page. Once configured, Veza Actions can be assigned to: * [Access Review events](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/veza-actions.md): Row approved, rejected, reassigned, or review completed * [Query rules and alerts](/4yItIzMvkpAvMVFAamTf/features/insights/rules-and-alerts.md): Threshold breaches and condition changes * [Lifecycle Management policies](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/lifecycle-management-notification-templates.md): Provisioning events and workflow notifications * [Access Request events](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/lifecycle-management-notification-templates.md): Request created, state changed, completed, or failed * [Event Subscriptions](/4yItIzMvkpAvMVFAamTf/administration/administration/events.md): System event alerts via email, Slack, Teams, ServiceNow, or custom webhooks See [Delivery Destinations](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations.md) for setup guides for each destination type. ## Email templates Administrators can customize email content for different notification types. Templates support: * HTML and CSS formatting * Dynamic placeholders for event-specific data * Custom branding and images * Handlebars syntax for advanced templating See [Notification Templates](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/email-templates.md) for customization guides and placeholder reference. ## Delivery settings Global settings control Access Review notification behavior: * **Digest notifications**: Consolidate pending review tasks into periodic summaries * **Review alerts**: Notify reviewers about new or newly-assigned reviews * **Reviewer deny list**: Exclude specific users from all review notifications * **Notification exclusions**: Exclude reviews from digests and alerts by label See [Delivery Settings](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/delivery-settings.md) for configuration options. ## Remediation workflows Veza Actions enable closed-loop remediation by connecting risk findings to action. When a [Rule](/4yItIzMvkpAvMVFAamTf/features/insights/rules-and-alerts.md) triggers on an Access Intelligence query, Veza Actions can automatically: * Create a Jira ticket or ServiceNow incident for the security team to investigate and remediate * Send a Slack or Teams notification to the responsible team for immediate awareness * Deliver a webhook payload to an internal remediation pipeline or SOAR platform This pattern applies across all Veza capabilities: human identity risks from [Access Intelligence](/4yItIzMvkpAvMVFAamTf/features/insights.md), non-human identity findings from [NHI Security](/4yItIzMvkpAvMVFAamTf/features/nhi.md), and governance decisions from [Access Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews.md). ## Next steps * [Notification Templates](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/email-templates.md): Customize notification content * [Delivery Destinations](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations.md): Configure Slack, Teams, Jira, and webhooks * [Delivery Settings](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/delivery-settings.md): Configure schedules and recipient controls * [Notification Templates API](/4yItIzMvkpAvMVFAamTf/developers/api/notification-templates/email-templates-api.md): Manage templates programmatically --- # Agent Instructions: 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/administration/administration/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.