From 0cba5f72a45665e2193086cfa3c6dfa18acfa10c Mon Sep 17 00:00:00 2001
From: brittonjohnson <75387582+brittonjohnson@users.noreply.github.com>
Date: Thu, 6 Mar 2025 13:48:13 -0700
Subject: [PATCH] Update unified-identity.rst

More info can be found here if needed. https://splunk.slack.com/archives/C059NSU6GSK/p1739989623418319
---
 splunkplatform/unified-id/unified-identity.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/splunkplatform/unified-id/unified-identity.rst b/splunkplatform/unified-id/unified-identity.rst
index 9e90d1406..aee93d25e 100644
--- a/splunkplatform/unified-id/unified-identity.rst
+++ b/splunkplatform/unified-id/unified-identity.rst
@@ -180,6 +180,10 @@ In Splunk Cloud Platform, create the custom role ``o11y_access`` and assign it t
 
 .. note:: If you do not create and assign the custom role ``o11y_access``, users receive the following error message when trying to log in to Splunk Observability Cloud: "You do not have access to Splunk Observability Cloud. Contact your Splunk Cloud Platform administrator for assistance."
 
+NOTE: When a new user from Splunk Support is added to your organization for troubleshooting an issue, they will appear as int_* in your organization. This is normal and is not an issue and is not a bug but a feature of Unified Identity. They will all normally have the same IP Address as well, since they are on a VPN. 
+
+
+
 If the user does not exist in Splunk Observability Cloud, the integration automatically creates a user in Splunk Observability Cloud and maps Splunk Cloud Platform roles to the following Splunk Observability Cloud roles:
 
 .. list-table::