AWS connect documentation change

Service: connect · 2026-05-19 · Documentation low

File: connect/latest/adminguide/dashboard-access-control.md

Summary

Replaced 'leverage' with 'use' in two instances and retained existing security note about hierarchy-based access limitations.

Security assessment

Changes are terminological (word substitution) with no modification to the documented security limitation regarding potential overexposure of data in conflicting access control setups.

Diff

diff --git a/connect/latest/adminguide/dashboard-access-control.md b/connect/latest/adminguide/dashboard-access-control.md
index f04d42c08..ae25ef702 100644
--- a//connect/latest/adminguide/dashboard-access-control.md
+++ b//connect/latest/adminguide/dashboard-access-control.md
@@ -11 +11 @@ How to enable hierarchy-based access controlAssign security profiles permissions
-You can leverage agent hierarchies to control who has access to view specific agents and their performance related metrics in dashboards and reports.
+You can use agent hierarchies to control who has access to view specific agents and their performance related metrics in dashboards and reports.
@@ -106 +106 @@ The following limitations apply when you use hierarchy-based access controls in
-    * If both security profiles have unique configurations for tag-based and hierarchy-based access control, we cannot enforce hierarchy-based access control effectively. This could allow users to access more data than intended in certain scenarios. In such cases, we recommend not granting access to Real-time and Historical reports for users with this type of access control setup, or just leverage hierarchy-based or tag-based controls to restrict users access.
+    * If both security profiles have unique configurations for tag-based and hierarchy-based access control, we cannot enforce hierarchy-based access control effectively. This could allow users to access more data than intended in certain scenarios. In such cases, we recommend not granting access to Real-time and Historical reports for users with this type of access control setup, or just use hierarchy-based or tag-based controls to restrict users access.