diff --git a/content/operate/kubernetes/deployment/openshift/openshift-operatorhub.md b/content/operate/kubernetes/deployment/openshift/openshift-operatorhub.md
index 9fb175e834..a555456efc 100644
--- a/content/operate/kubernetes/deployment/openshift/openshift-operatorhub.md
+++ b/content/operate/kubernetes/deployment/openshift/openshift-operatorhub.md
@@ -29,7 +29,7 @@ To see which version of Redis Enterprise for Kubernetes supports your OpenShift
 
     Only one namespace per operator is supported.
 
-4. Update the **channel** with the version you're installing. 
+4. Update the **channel** with the version you're installing.
 
     For more information about specific versions, see the [release notes]({{< relref "/operate/kubernetes/release-notes/" >}}).
 
@@ -66,11 +66,15 @@ You only need to install the SCC once, but you must not delete it.
 After the install, the OperatorHub automatically uses the constraint for Redis Enterprise node pods.
 
 {{< note >}}
-**Known Limitation** - The automatic use of the security constraint is limited. The
-Redis Enterprise must be named `rec` for the constraint to be used automatically.  **Use the cluster name `rec` when deploying with the OperatorHub.**
+If you are using the recommended RedisEnterpriseCluster name of `rec`, the SCC is automatically bound to the RedisEnterpriseCluster after install.
+
+If you choose a different name for the RedisEnterpriseCluster, or override the default service account name, you must manually bind the SCC to the RedisEnterpriseCluster’s service account:
+
+  ```sh
+  oc adm policy add-scc-to-user redis-enterprise-scc-v2 \
+  system:serviceaccount:<my-project>:<rec-service-account-name>
+  ```
 
-If you require a different name, you must grant the SCC to the project
-namespace.
 {{< /note >}}
 
 ## Create Redis Enterprise custom resources