https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_security_for_kubernetes/4.10/html/operating/using-policies-to-provide-security#enable-admission-controller-enforcement-existing-cluster_use-admission-controller-enforcement

In section 5.2.3 , the instruction to enable says

admissionControl.enforce value to false

This is probably a bug . We can see that  false  is used in section 5.2.5 to disable, not to enable.

5.2.3. Viewing and enabling admission controller enforcement on an existing cluster 

You can view whether admission controller enforcement was enabled on a cluster or change the enforcement behavior after installation.
Procedure

1. For a cluster that was installed by using the Operator, in the SecuredCluster custom resource (CR), edit the spec.admissionControl.enforcement parameter to Enabled.
2. For a cluster that was installed by using Helm, in the values-public.yaml file, set the admissionControl.enforce value to false and run the following command:

5.2.5. Disabling admission controller enforcement on a cluster 

You can disable admission controller enforcement on a cluster when installing RHACS. For clusters that you did not install by using the Operator or Helm, you can disable admission controller enforcement from the Clusters view on the Red Hat Advanced Cluster Security for Kubernetes (RHACS) portal.
Procedure

1. For a cluster that was installed by using the Operator, in the SecuredCluster custom resource (CR), edit the spec.admissionControl.enforcement parameter to Disabled.
2. For a cluster that was installed by using Helm, in the values-public.yaml file, set the admissionControl.enforce value to false and run the following command:

(note two occureneces)