# Boolean constraint

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

A Google Cloud constraint that is either enforced or not enforced, with no list of values. A policy that sets a boolean constraint turns one behavior on or off for a resource and its descendants. It is either on or off.

## An example, sourced

Google documents that legacy managed constraints can have boolean rules, which "can allow all values, deny all values, or determine if a constraint is enforced or not enforced." Custom constraints are described as functionally similar to managed constraints with boolean parameters, and are either enforced or not enforced. Managed constraints can have list or boolean parameters set by the enforcing service.

## Why it matters here

Boolean constraints are the simplest to dry-run and to reason about. Several library entries, such as disabling service account key creation, are of this kind. Boolean constraints are the easiest to dry-run and reason about, since a project is either inside the rule or outside it. Several library entries, such as the one disabling service account key creation, are of this kind.

## Related pages

- [Custom constraint: meaning and an example](/glossary/custom-constraint/)
- [Dry-run mode: meaning and an example](/glossary/dry-run-mode/)
- [IAM deny policy: meaning and an example](/glossary/iam-deny-policy/)
- [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/boolean-constraint/
