From 8c1abd3b9204872b395a093357e7958df6634a53 Mon Sep 17 00:00:00 2001
From: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com>
Date: Mon, 24 May 2021 18:11:49 -0400
Subject: [PATCH] [DOCS] Fleet and Endpoint Security require a Transform,
 appropriate configuration is needed (#693) (#699)

* Adding section for required node roles.

* Adding missing article.

* Added Janeen's feedback.
---
 docs/getting-started/sec-app-requirements.asciidoc | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/getting-started/sec-app-requirements.asciidoc b/docs/getting-started/sec-app-requirements.asciidoc
index e5034066a8..afe2f504a3 100644
--- a/docs/getting-started/sec-app-requirements.asciidoc
+++ b/docs/getting-started/sec-app-requirements.asciidoc
@@ -17,6 +17,13 @@ https://www.elastic.co/cloud/elasticsearch-service[cloud deployment],
 available on Azure, AWS, and GCP. You can {ess-trial}[try it out for free].
 ==============
 
+[discrete]
+[[node-role-requirements]]
+== Node role requirements
+To use Elastic Security, at least one node in your Elasticsearch cluster must have the {ref}/transform-settings.html[`transform` role]. Nodes are automatically given this role when they’re created, so changes are not required if default role settings remain the same. This applies to on-premise and cloud deployments.
+
+Changes might be required if your nodes have customized roles. When updating node roles, nodes are only assigned the roles you specify, and default roles are removed. If you need to reassign the `transform` role to a node, {ref}/modules-node.html#transform-node[create a dedicated transform node].
+
 [discrete]
 == {kib} space and index privileges