---
updatedAt: 2026-10-04T12:08:02.000Z
agentTools:
projectIndex: https://docs.lmnl.app/v2/llms.txt
---
# Disable Compliance Alerts for Address Screening
**Liminal Vaults** [Owners](https://docs.lmnl.app/v2/docs/user-roles-and-teams#/user-roles) can configure destination address screening protocols with integrated app support from [Cube3](https://www.cube3.ai/) and [Cyvers](https://cyvers.ai/) to evaluate cyber, fraud, and compliance risks.
Refer to the [Address Screening with Cube3 and Cyvers](https://docs.lmnl.app/v2/docs/address-screening-with-cube3-and-cyvers) guide to learn how to configure address screening for your organisation.
# Ignoring Compliance Alerts
When you enable the **Screen all destination addresses for security-related risks, such as compliance, fraud, and hacks** feature, all transactions initiated through the [Liminal Express API](https://docs.lmnl.app/v2/reference/liminal-express-apis#/) are evaluated against the configured minimum risk score.
* Transactions exceeding the minimum risk score are blocked,
* The [Create Transaction Request API](https://docs.lmnl.app/v2/reference/sendmanytransaction-1#/) returns a `422 Unprocessable Entity` response, and
* Alerts and warnings are generated to notify you of potential issues.
The final risk score for each destination address screening is determined based on the following alert categories:
1. **Cyvers**: Security, Scam, and Compliance alerts.
2. **Cube3**: Cyber, Fraud, and Compliance alerts.
**Compliance scoring**
The compliance regulation screens the destination address and assigns a transaction risk score based on risk management requirements and blockchain regulations, like KYC, Travel Rule, and AML. This allows organisations to enforce regulatory standards during transactions.
Refer to the [Address Screening with Cube3 and Cyvers](https://docs.lmnl.app/v2/docs/address-screening-with-cube3-and-cyvers) guide to learn more.
**Owners** can choose to ignore compliance alerts and base risk evaluations solely on security, scam, cyber, and fraud categories.
# Disable Compliance Alerts
The **Ignore Compliance Alerts** feature is disabled for all organisations by default. When you enable it and ignore compliance alerts:
* Compliance scores are excluded from the total risk score.
* The total risk score is calculated based only on the scam, fraud, and cyber categories.
The final risk score is determined by the highest converted score between the fraud and cyber categories.
* The compliance score is still calculated and remains visible during destination address whitelisting, transaction initiation, approval, and signing, for reference.
* Transaction blocking and warnings based on compliance alerts are ignored.
* For transactions that would otherwise be blocked due to compliance alerts, the [Create Transaction Request](https://docs.lmnl.app/v2/reference/sendmanytransaction-1#/) API returns a `201 OK` response.
## Prerequisite
1. You are an **Owner**.
2. You have enabled address screening for all destination addresses. Refer to the [Configure Address Screening](https://docs.lmnl.app/v2/docs/set-personalised-thresholds-or-switch-off-address-screening#/configure-address-screening) section to configure address screening and assign a personalised threshold.
## Steps
To disable **Compliance** alerts for address screening from **Cube3** and **Cyvers**, follow the steps below:
1. Sign in to your **Liminal Vaults** [account](https://vaults.lmnl.app/).
2. Navigate to **Settings** on the left navigation bar.
3. Scroll down to the **Address Screening** section and click **Edit**.
4. **Toggle on** the **Ignore Compliance Alerts** feature to exclude compliance scores from risk calculation.
5. Enter the 2FA confirmation code as prompted.
6. Click **Ok** to confirm the action in the pop-up.
7. Click **Save** to apply the updated Address Screening configuration.
**Note**
You can **toggle off** the **Ignore Compliance Alerts** policy at any time to include compliance scores within the risk score calculation. Transactions that exceed the configured compliance score threshold will be blocked, and alerts will be triggered through the [Liminal Express API](https://docs.lmnl.app/v2/reference/liminal-express-apis#/) when enabled.