> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zwiron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trust gate policy

> Configure warn vs block when a quality gate fails after MOVE — Settings Trust gate policy.

## Overview

**Trust gate policy** controls what happens when a **quality gate** fails after MOVE (sync / detect). Configure it in organization Settings—not on each incident.

To open the setting:

1. Select **Account → Settings** (or **Settings** in the sidebar).
2. Open the **General** tab (organization settings).
3. Find **Trust gate policy**.

***

## Policy options

| UI value | Behavior |
| - | - |
| **Warn — open incident, stale cert, trust=warn** | Job continues. An incident is opened; certification is marked stale; Job Trust status is **warn**. |
| **Block — same as warn, escalate trust=blocked** | Same incident / cert signals as warn, and Job Trust status escalates to **blocked** (product may fail / block the Job path accordingly). |

The underlying org setting is `trust_block_on_gate` (`false` = warn, `true` = block).

<Note>
  Only failures marked as quality gates participate in this policy. Non-gated check failures do not produce a gate warn/block decision by themselves.
</Note>

***

## When to use warn vs block

| Stage | Recommendation |
| - | - |
| Building coverage / early DQ | **Warn** — surface incidents without stopping every pipeline |
| Critical assets with trusted tests | **Block** — prevent bad data from being treated as good |

Save organization settings after changing the policy (**Save** on the General card).

***

## Related articles

* [Trust overview](/trust/overview)
* [Trust incidents](/trust/incidents)
* [Data Quality](/platform/data-quality)
* [Jobs](/platform/jobs)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.