AWS Security ChangesHomeSearch

AWS connect documentation change

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

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

Summary

Updated product name references from 'Amazon Connect' to 'Connect Customer' throughout the document.

Security assessment

Only branding terminology was changed; the actual security mechanisms (hierarchy-based access control) remain unchanged with no evidence of security fixes or enhancements.

Diff

diff --git a/connect/latest/adminguide/dashboard-access-control.md b/connect/latest/adminguide/dashboard-access-control.md
index 9065660e0..f04d42c08 100644
--- a//connect/latest/adminguide/dashboard-access-control.md
+++ b//connect/latest/adminguide/dashboard-access-control.md
@@ -9 +9 @@ How to enable hierarchy-based access controlAssign security profiles permissions
-# Apply hierarchy-based access control to dashboards and reports in Amazon Connect
+# Apply hierarchy-based access control to dashboards and reports in Connect Customer
@@ -13 +13 @@ You can leverage agent hierarchies to control who has access to view specific ag
-Hierarchy-based access control enables you to configure granular access to users based on the [agent hierarchy](./agent-hierarchy.html) that is assigned to a user. You can [configure](./hierarchy-based-access-control.html) hierarchy-based access controls by using the API/SDK or the Amazon Connect admin website.
+Hierarchy-based access control enables you to configure granular access to users based on the [agent hierarchy](./agent-hierarchy.html) that is assigned to a user. You can [configure](./hierarchy-based-access-control.html) hierarchy-based access controls by using the API/SDK or the Connect Customer admin website.
@@ -84 +84 @@ OR
-Additionally, the user will need permissions to access resources. The following image shows an example of security profile permissions that grant users the ability to view routing profiles, queues, and Amazon Connect user accounts. **Routing profiles - View** , **Queues - View** , and **Users - View** are selected.
+Additionally, the user will need permissions to access resources. The following image shows an example of security profile permissions that grant users the ability to view routing profiles, queues, and Connect Customer user accounts. **Routing profiles - View** , **Queues - View** , and **Users - View** are selected.