diff --git a/docs/reference/scripting/security.asciidoc b/docs/reference/scripting/security.asciidoc
index 385d0217686f..426305df562a 100644
--- a/docs/reference/scripting/security.asciidoc
+++ b/docs/reference/scripting/security.asciidoc
@@ -79,9 +79,15 @@ security of the Elasticsearch deployment.
 === Allowed script types setting
 
 Elasticsearch supports two script types: `inline` and `stored` (<<modules-scripting-using>>).
-By default both types of scripts are allowed to be executed. To limit the types of scripts
-that can run, set `script.allowed_types` to `inline`, `stored`, or `none`. For example,
-to run `inline` scripts but not `stored` scripts, specify:
+By default, {es} is configured to run both types of scripts. 
+To limit what type of scripts are run, set `script.allowed_types` to `inline` or `stored`. 
+To prevent any scripts from running, set `script.allowed_types` to `none`.
+
+IMPORTANT: If you use {kib}, set `script.allowed_types` to `both` or `inline`. 
+Some {kib} features rely on inline scripts and do not function as expected 
+if {es} does not allow inline scripts.
+
+For example, to run `inline` scripts but not `stored` scripts, specify:
 
 [source,yaml]
 ----
@@ -90,6 +96,7 @@ script.allowed_types: inline <1>
 <1> This will allow only inline scripts to be executed but not stored scripts
 (or any other types).
 
+
 [[allowed-script-contexts-setting]]
 [discrete]
 === Allowed script contexts setting