From 65fe4d417fb792509accb7c28d9b9d39cbceb9ea Mon Sep 17 00:00:00 2001
From: Joe Peeples <joe.peeples@elastic.co>
Date: Mon, 22 Jan 2024 11:14:17 -0500
Subject: [PATCH] Remove outdated tip about custom ML jobs (#4639)

(cherry picked from commit 40d913a1c777a5dadec43f9e6958af15053e64f1)
---
 docs/advanced-entity-analytics/machine-learning.asciidoc | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docs/advanced-entity-analytics/machine-learning.asciidoc b/docs/advanced-entity-analytics/machine-learning.asciidoc
index 7a3cb11fb1..673997ef3b 100644
--- a/docs/advanced-entity-analytics/machine-learning.asciidoc
+++ b/docs/advanced-entity-analytics/machine-learning.asciidoc
@@ -22,10 +22,6 @@ If you have the `machine_learning_admin` role, you can use the *ML job settings*
 [role="screenshot"]
 image::images/ml-ui.png[ML job settings UI on the Alerts page]
 
-TIP: To add a custom job to the *ML job settings* interface, add `Security` to
-the job's `Groups` field (*{kib}* -> *{ml-cap}* -> *Create/Edit job* -> *Job
-details*).
-
 [float]
 [[manage-ml-rules]]
 === Manage {ml} detection rules