---
title: Disable policy enforcement
description: "Temporarily disable PingIDM back-end policy enforcement to import data that doesn't meet validation requirements"
component: pingidm
version: 7.5
page_id: pingidm:objects-guide:disabling-policies
canonical_url: https://docs.pingidentity.com/pingidm/8.1/objects-guide/disabling-policies.html
llms_txt: https://docs.pingidentity.com/pingidm/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Data Object Model", "Policy"]
superseded_by: https://docs.pingidentity.com/pingidm/8.1/objects-guide/disabling-policies.html
---

# Disable policy enforcement

*Policy enforcement* is the automatic validation of data when it is created, updated, or patched. In certain situations you might want to disable policy enforcement temporarily. You might, for example, want to import existing data that does not meet the validation requirements with the intention of cleaning up this data at a later stage.

You can disable policy enforcement by setting `openidm.policy.enforcement.enabled` to `false` in your `resolver/boot.properties` file. This setting disables policy enforcement in the back-end only, and has no impact on direct policy validation calls to the Policy Service (which the UI makes to validate input fields). So, with policy enforcement disabled, data added directly over REST is not subject to validation, but data added with the UI is still subject to validation.

You should not disable policy enforcement permanently, in a production environment.