diff --git a/rfcs/0010-multi-tenant-workload-identity/README.md b/rfcs/0010-multi-tenant-workload-identity/README.md
index d975980f51e3c7ed87997afca89262fce39e6866..5c867717813a959bbd85e8b51f7260e48863b779 100644
--- a/rfcs/0010-multi-tenant-workload-identity/README.md
+++ b/rfcs/0010-multi-tenant-workload-identity/README.md
@@ -601,11 +601,7 @@ To enable using the new `serviceAccountName` fields, we propose introducing
 a feature gate called `ObjectLevelWorkloadIdentity` in the controllers that
 would support the feature. In the first release we should make it opt-in so
 cluster admins can consciously roll it out. If the feature gate is disabled
-and users set the field in Flux APIs that use the field only for this feature,
-a terminal error should be returned. If the feature gate is disabled and users
-set the field in Flux APIs that use the field for other purposes, like in the
-case of the `OCIRepository` and `ImageRepository` APIs, the controller should
-just log a warning and ignore the field.
+and users set the field a terminal error should be returned.
 
 ### Workload Identity Library