From dd6ae71f53a4dca49565834d9f5e5cf0b67844d9 Mon Sep 17 00:00:00 2001
From: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
Date: Thu, 7 Aug 2025 12:53:21 -0600
Subject: [PATCH 1/2] Add youtube video for file-based realm user authentiation
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

👋 howdy, team! Adds [this latest Support troubleshooting video](https://www.youtube.com/watch?v=sueO7sz1buw&list=PL_mJOmq4zsHbQlfEMEh_30_LuV_hZp-3d&index=1) to the [File-based user authentication](https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/file-based) page
---
 .../users-roles/cluster-or-deployment-auth/file-based.md        | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md b/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md
index 49dcc45881..e8b7a1dad1 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md
@@ -20,6 +20,8 @@ The `file` realm is useful as a fallback or recovery realm. For example in cases
 
 You can configure only one file realm on {{es}} nodes.
 
+See [this video](https://www.youtube.com/watch?v=sueO7sz1buw) for a walkthrough on enabling a file realm user for recovery. 
+
 ::::{important}
 * In self-managed deployments, as the administrator of the cluster, it is your responsibility to ensure the same users are defined on every node in the cluster. The {{stack}} {{security-features}} do not deliver any mechanism to guarantee this.
 * You can't add or manage users in the `file` realm using the [user APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security), or using the {{kib}} **Management > Security > Users** page.

From 89481bb5a0c94e44b3f885ae1387a3b6e0677158 Mon Sep 17 00:00:00 2001
From: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
Date: Thu, 7 Aug 2025 15:49:47 -0600
Subject: [PATCH 2/2] =?UTF-8?q?feedback=20=F0=9F=99=8F?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
---
 .../users-roles/cluster-or-deployment-auth/file-based.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md b/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md
index e8b7a1dad1..6aace3d93a 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md
@@ -20,7 +20,7 @@ The `file` realm is useful as a fallback or recovery realm. For example in cases
 
 You can configure only one file realm on {{es}} nodes.
 
-See [this video](https://www.youtube.com/watch?v=sueO7sz1buw) for a walkthrough on enabling a file realm user for recovery. 
+Refer to [enabling a file realm user for recovery](https://www.youtube.com/watch?v=sueO7sz1buw) for a video walkthrough. 
 
 ::::{important}
 * In self-managed deployments, as the administrator of the cluster, it is your responsibility to ensure the same users are defined on every node in the cluster. The {{stack}} {{security-features}} do not deliver any mechanism to guarantee this.