> 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/administration/administration/notifications/destinations.md).

# Delivery Destinations

Veza Actions send notifications to external systems when events occur in Access Reviews, Rules and Alerts, Lifecycle Management, Access Requests, and CSV upload integrations. Configure destinations on the **Integrations** > *Veza Actions* page.

## Available integrations

| Integration                                                                                                        | Use Case                                         |
| ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------ |
| [Email](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/email.md)                   | Send notifications to individual email addresses |
| [Slack App](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/slack-app.md)                              | Direct messages to reviewers via Slackbot        |
| [Slack Webhook](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/slack.md)           | Channel posts for team visibility                |
| [Microsoft Teams](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/teams.md)         | Channel posts via webhook or Power Automate      |
| [Microsoft Teams App](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/teams-app.md) | Direct messages to reviewers via Veza bot        |
| [Jira](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md)                     | Ticket creation for remediation tracking         |
| [ServiceNow](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/servicenow.md)         | Incident and change management                   |
| [Custom Webhooks](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/webhooks.md)      | Any HTTP endpoint or automation trigger          |

## Getting started

1. Go to **Integrations** > *Veza Actions* > **Add Veza Action**
2. Select the destination type and enter connection details
3. Test the connection, then save
4. Assign the action to events in Access Reviews, Rules, or LCM policies

## See also

* [Veza Actions for Access Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/veza-actions.md)
* [Rules and Alerts](/4yItIzMvkpAvMVFAamTf/features/insights/rules-and-alerts.md)
* [LCM Notifications](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/lifecycle-management-notification-templates.md)
* [CSV Upload Notifications](/4yItIzMvkpAvMVFAamTf/integrations/integrations/csv.md#notifications)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.