diff --git a/content/en/docs/refguide/modeling/security/app-security/strict-mode.md b/content/en/docs/refguide/modeling/security/app-security/strict-mode.md
index 96e90fe5fd9..21bc5eb51c4 100644
--- a/content/en/docs/refguide/modeling/security/app-security/strict-mode.md
+++ b/content/en/docs/refguide/modeling/security/app-security/strict-mode.md
@@ -35,6 +35,13 @@ When strict mode is enabled, the following [client APIs](/apidocs-mxsdk/apidocs/
 
 The APIs will be disabled on the Runtime, which means that these APIs cannot be invoked in online apps via JavaScript actions or the browser's console. If any of these APIs are used in a JavaScript action, consider using a nanoflow instead.
 
+### Restricted Client APIs in Platform Supported Widgets
+
+In strict mode, some actions in platform-supported widgets are restricted because they rely on blocked client APIs.
+
+* [File Uploader](/appstore/modules/file-uploader/) – The delete action does not work in strict mode because it uses `data.remove`. To work around this restriction, create a custom button and use a nanoflow to delete the file object. For guidance, see the [Enable Custom Buttons](/appstore/modules/file-uploader/#enable-custom-buttons) section in *File Uploader*.
+* [Web Actions](/appstore/modules/web-actions/) – The **Take picture** action does not work in strict mode because it uses `data.commit` to create the object.
+
 ## Save And Cancel Changes Action {#save-and-cancel}
 
 In strict mode, your model is analyzed by Studio Pro to ensure that only entities within editable widgets can be saved or rolled back during save or cancel actions.