AWS connect documentation change
Summary
Expanded access controls documentation from tag-based to include hierarchy-based access controls for Login/Logout reports
Security assessment
Added detailed instructions for implementing hierarchy-based access controls, which improves security documentation but doesn't fix existing vulnerabilities.
Diff
diff --git a/connect/latest/adminguide/login-logout-reports.md b/connect/latest/adminguide/login-logout-reports.md index 8e67cc4ad..8820a1f2d 100644 --- a//connect/latest/adminguide/login-logout-reports.md +++ b//connect/latest/adminguide/login-logout-reports.md @@ -7 +7 @@ -Why your Login/Logout report may appear incorrectReport limit: 10,000 rowsRequired permissionsGenerate a Login/Logout reportEdit a Saved Login/Logout ReportDownload a Login/Logout report as a CSV fileShare a Login/Logout reportSchedule a Login/Logout reportDelete a Saved Login/Logout reportTag-based access controls +Why your Login/Logout report may appear incorrectReport limit: 10,000 rowsRequired permissionsGenerate a Login/Logout reportEdit a Saved Login/Logout ReportDownload a Login/Logout report as a CSV fileShare a Login/Logout reportSchedule a Login/Logout reportDelete a Saved Login/Logout reportTag-based and hierarchy-based access controls @@ -33 +33 @@ The Login/Logout report displays the login and logout information for the users - * Tag-based access controls + * Tag-based and hierarchy-based access controls @@ -258 +258 @@ Too many reports in your report library? If you no longer want to use a saved re -## Tag-based access controls on the Login/Logout report +## Tag-based and hierarchy-based access controls for the Login/Logout report @@ -262 +262,5 @@ To use tags to control access to users on the agent Login/Logout report, you mus -After your resource tags, access control tags, and permissions have been appropriately configured, you will have access controls applied to users for the Login/Logout report. +After you configure your resource tags, access control tags, and permissions, Connect Customer applies tag-based access controls to users for the Login/Logout report. + +To use agent hierarchy-based access control for the Login/Logout report, you must first complete several configuration steps. Configure agent hierarchy in Connect Customer, assign users to a hierarchy, configure resource permissions, and set up hierarchy-based access controls. For more information, see [Apply hierarchy-based access control to dashboards and reports in Connect Customer](./dashboard-access-control.html). + +After you configure the agent hierarchy, assign users to a hierarchy, and configure user permissions, Connect Customer applies hierarchy-based access controls to users for the Login/Logout report.