# List constraint

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

A Google Cloud constraint whose policy holds a list of allowed or denied values, such as a list of permitted domains or Regions. In current Google documentation these are legacy managed constraints with list rules. Merged across levels, values from child policies combine with the parent's.

## An example, sourced

Google documents that legacy managed constraints can have list rules, "a collection of allowed or denied values," and that these legacy constraints "were previously known as list constraints." The values are expressed as hierarchy subtree strings. The page names the constraint constraints/compute.trustedImageProjects as an example of one that takes a list. Google documents that when policies merge and a value conflicts, the DENY value takes precedence, and that default behavior is never merged but replaced when a policy is set.

## Why it matters here

List constraints merge across the hierarchy, and deny values win in a conflict. Read the effective policy at the project before trusting an allow list set higher up. Because values merge, an allow list set high up can grow lower down. Read the effective policy on the project before trusting it.

## Related pages

- [Boolean constraint: meaning and an example](/glossary/boolean-constraint/)
- [Custom constraint: meaning and an example](/glossary/custom-constraint/)
- [Dry-run mode: meaning and an example](/glossary/dry-run-mode/)
- [All of them](/glossary/)

## Sources

- https://cloud.google.com/resource-manager/docs/organization-policy/overview (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/list-constraint/
