diff --git a/content/rancher/v2.x/en/admin-settings/authentication/ping-federate/_index.md b/content/rancher/v2.x/en/admin-settings/authentication/ping-federate/_index.md
index b0fd2864def..bec28e284a5 100644
--- a/content/rancher/v2.x/en/admin-settings/authentication/ping-federate/_index.md
+++ b/content/rancher/v2.x/en/admin-settings/authentication/ping-federate/_index.md
@@ -43,4 +43,9 @@ If your organization uses Ping Identity Provider (IdP) for user authentication,
 
     >**Note:** You may have to disable your popup blocker to see the IdP login page.
 
-**Result:** Rancher is configured to work with PingIdentity. Your users can now sign into Rancher using their PingIdentity logins.
\ No newline at end of file
+**Result:** Rancher is configured to work with PingIdentity. Your users can now sign into Rancher using their PingIdentity logins.
+
+>**Ping Identity Provider Caveats:** 
+>
+>- IdP does not support search or lookup. When adding users to [clusters]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/editing-clusters/) or [projects]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/), the exact IDs must be entered correctly.
+>- When adding users to [clusters]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/editing-clusters/) or [projects]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/), group IDs are not supported unless the admin who turned on access control is a member of the group.
\ No newline at end of file
diff --git a/content/rancher/v2.x/en/k8s-in-rancher/editing-clusters/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/editing-clusters/_index.md
index 555cf2c180d..f2d068e09b9 100644
--- a/content/rancher/v2.x/en/k8s-in-rancher/editing-clusters/_index.md
+++ b/content/rancher/v2.x/en/k8s-in-rancher/editing-clusters/_index.md
@@ -7,6 +7,11 @@ weight: 3015
 
 Following cluster creation, you can add users as cluster members so that they can access its resources.
 
+>**Ping Identity Provider Caveats:**
+>
+>- IdP does not support search or lookup. When adding users to clusters, the exact IDs must be entered correctly.
+>- When adding users to a cluster, group IDs are not supported unless the admin who turned on access control is a member of the group.
+
 1. From the **Global** view, open the cluster that you want to add members to.
 
 2. From the main menu, select **Members**. Then click **Add Member**.
diff --git a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md
index bc2819808e3..609d59e2cec 100644
--- a/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md
+++ b/content/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/_index.md
@@ -11,6 +11,11 @@ After projects are created, there are certain aspects that can be changed later.
 
 Following project creation, you can add users as project members so that they can access its resources.
 
+>**Ping Identity Provider Caveats:**
+>
+>- IdP does not support search or lookup. When adding users to projects, the exact IDs must be entered correctly.
+>- When adding users to a project, group IDs are not supported unless the admin who turned on access control is a member of the group.
+
 1. From the **Global** view, open the project that you want to add members to.
 
 2. From the main menu, select **Members**. Then click **Add Member**.