# Remediation Actions

## Overview

Remediation actions enable you to take immediate action on findings identified by Veza queries and dashboards. When reviewing a query or dashboard, you can create tickets or send messages through integrated systems to initiate remediation workflows.

Veza integrates with Jira, ServiceNow, and Slack so you can create tickets or post messages for findings that need attention.

![Access Security Reference Architecture: Veza ingests access metadata into the Access Graph, computes risk scores, surfaces risks in dashboards, and enables Identity Ops to open ServiceNow tickets for remediation.](/files/T5CnHE5ZL2nnyfOg4QFf)

### When to use remediation

Use remediation when you need to act on specific findings. For example, after reviewing a dashboard and spotting a risk that needs attention. Common scenarios include:

* **Escalating critical findings**: A dashboard shows service accounts with excessive permissions. Click **Remediate** to create a Jira ticket assigned to the team responsible for that service.
* **Coordinating across teams**: A query identifies users with stale access to a sensitive database. Share the finding via Slack so the responsible team can investigate.
* **Creating an audit trail**: A compliance review reveals misconfigured storage buckets. Create a ServiceNow incident to document the finding and track remediation through your ITSM workflow.

{% hint style="info" %}
Remediation creates a one-time ticket or message for a specific finding. For ongoing monitoring that triggers automatically when conditions change, use [Rules and Alerts](/4yItIzMvkpAvMVFAamTf/features/insights/rules-and-alerts.md) instead.
{% endhint %}

## How it works

When you click **Remediate** on a dashboard or query, Veza opens a modal where you choose a channel and configure the notification:

1. **Select a channel**: Choose Jira, ServiceNow, or Slack from the **Remediate** dropdown.
2. **Choose Veza Actions**: Pick one or more configured Veza Actions as the delivery destination. Each selected action creates a separate ticket or message.
3. **Add context**: Optionally add notes, and (for Jira) assign a team member.
4. **Preview and submit**: Review the live preview of the ticket or message content, then click **Create**.

After submission, Veza polls the notification status and displays a toast notification confirming success or reporting any errors.

Each remediation notification includes a **title** (the query or dashboard name), a **direct link** to the source in Veza, and any **notes** you added. The message body uses a standard format that varies by channel. See the channel-specific guides below for details and examples.

{% hint style="info" %}
Remediation notifications use a fixed message format. Unlike [alert email templates](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/email-templates/customizing-templates.md), the body structure of remediation tickets and messages cannot be customized. You can control the title, notes, and delivery destination, but not the overall message layout.
{% endhint %}

{% hint style="info" %}
**Private queries and public dashboards**: When a dashboard is made public, any private queries on the dashboard are automatically excluded. Users viewing a public dashboard will not see tiles for queries they do not have access to. There is no "not found" or empty state for those tiles. Dashboard-level remediation references the dashboard name and link, not individual query results. For dashboards shared across teams, queries that require integrations outside the recipient team's scope are also hidden from that team's view.
{% endhint %}

## Remediation channels

Remediation supports three notification channels. See each guide for a full end-to-end walkthrough:

| Channel        | What it creates                                              | Options                                              | Guide                                                                                                             |
| -------------- | ------------------------------------------------------------ | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Jira**       | Jira ticket with finding details and link                    | Select Veza Action(s), assign team member, add notes | [Remediate via Jira](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-jira.md)             |
| **ServiceNow** | ServiceNow incident with finding details and link            | Select Veza Action(s), add notes                     | [Remediate via ServiceNow](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-servicenow.md) |
| **Slack**      | Message posted to configured Slack channel (not individuals) | Select Veza Action(s), add notes                     | [Remediate via Slack](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-slack.md)           |

Available channels depend on which Veza Actions are configured in **Integrations** > **Veza Actions**. If no actions are configured for a channel type, that option will not appear in the **Remediate** dropdown.

## Prerequisites

Before using remediation actions, ensure:

* At least one [Veza Action](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations.md) is configured for a supported channel ([Jira](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md), [ServiceNow](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/servicenow.md), or [Slack](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/slack.md))
* Your account has the required remediation permissions

### Required permissions

Remediation requires both **view** and **create** permissions for the target type:

| Target type | Required permissions                                                       |
| ----------- | -------------------------------------------------------------------------- |
| Query       | `assessment_query:remediate:view`, `assessment_query:remediate:create`     |
| Dashboard   | `assessment_reports:remediate:view`, `assessment_reports:remediate:create` |

If you do not see the **Remediate** button, contact your Veza administrator to verify your role includes these permissions.

## Troubleshooting

### Remediate button is not visible

| Cause               | Solution                                                                                                                                                                                                             |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Missing permissions | Your role must include `assessment_query:remediate:view` and `assessment_query:remediate:create` (for queries) or the equivalent `assessment_reports` permissions (for dashboards). Contact your Veza administrator. |

### No channels available in dropdown

| Cause                      | Solution                                                                                                                                                                                                                                                                                                                                                                                   |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| No Veza Actions configured | Configure at least one [Jira](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md), [ServiceNow](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/servicenow.md), or [Slack](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/slack.md) Veza Action in **Integrations** > **Veza Actions**. |

### Notification failed or errored

After submitting a remediation, Veza displays a toast notification with the result. Possible statuses:

| Status      | Meaning                                                                                       |
| ----------- | --------------------------------------------------------------------------------------------- |
| **Success** | The ticket was created or the message was sent.                                               |
| **Failed**  | The target system rejected the request. Verify the Veza Action configuration and credentials. |
| **Error**   | An unexpected error occurred. Check the Veza Action connection and retry.                     |

If a notification fails, verify the Veza Action is still valid by testing it from **Integrations** > **Veza Actions**.

## Direct actions

In addition to notification channels, Veza supports direct remediation actions that execute against the target identity provider. Direct actions are available for queries that return a supported user entity type, and require Provisioning to be enabled for the target integration.

### Disable Accounts (Early Access)

The **Disable Accounts** action disables user accounts in the source identity provider directly from a query result. This is a bulk, immediate action with no approval step — review the full documentation before enabling it on a production query.

See [Disable Accounts](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-disable-accounts.md) for the complete guide, including prerequisites, workflow, supported integrations, and how to interpret the audit log.

## See also

* [Disable Accounts](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-disable-accounts.md)
* [Remediate via Jira](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-jira.md)
* [Remediate via ServiceNow](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-servicenow.md)
* [Remediate via Slack](/4yItIzMvkpAvMVFAamTf/features/insights/remediation-actions/remediation-slack.md)
* [Veza Actions: Delivery destinations](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations.md)
* [Jira Veza Action](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md) (setup and example notifications)
* [ServiceNow Veza Action](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/servicenow.md) (setup and example notifications)
* [Slack Veza Action](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/slack.md) (setup and example messages)
* [Dashboards](/4yItIzMvkpAvMVFAamTf/features/insights/dashboards.md)
* [Risks](/4yItIzMvkpAvMVFAamTf/features/insights/risks.md)
* [Rules and Alerts](/4yItIzMvkpAvMVFAamTf/features/insights/rules-and-alerts.md)


---

# 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/features/insights/remediation-actions.md?ask=<question>
```

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.