AWS connect documentation change
Summary
Added documentation for granular access control via agent hierarchies and removed 'Preview' label from a feature
Security assessment
The change introduces documentation for hierarchy-based access control, a security feature that restricts data visibility based on organizational groups. While this improves security practices, there is no evidence of addressing a specific vulnerability.
Diff
diff --git a/connect/latest/adminguide/amazon-connect-release-notes.md b/connect/latest/adminguide/amazon-connect-release-notes.md index 5f662a5f4..03e899ab9 100644 --- a//connect/latest/adminguide/amazon-connect-release-notes.md +++ b//connect/latest/adminguide/amazon-connect-release-notes.md @@ -12,0 +13,4 @@ We recommend subscribing to the RSS feed so updates to these notes are delivered +### Enforce granular access control by using agent hierarchies + +You can enforce granular access control based on a specific agent hierarchy. Assigning hierarchies to a user allows you to define organizational groups that a user belongs to and you can enable granular access controls by allowing users to only view metrics for agents within their hierarchy or a specific assigned hierarchy. For example, you can configure hierarchy groups and levels for a team, and only users assigned to a hierarchy group within that team will be able to see metrics for those agents. For more information, see [Apply hierarchy-based access control to dashboards and reports in Amazon Connect](./dashboard-access-control.html). + @@ -757 +761 @@ For more information, see [View generative AI-powered post-contact summaries in -In addition to tags, you can enable granular access controls for users by [configuring agent](./agent-hierarchy.html) hierarchies within the Amazon Connect admin website. Assigning hierarchies to a user allows you to define organizational groups that a user belongs to, and you can restrict users from accessing others outside their hierarchy by configure granular permissions. For example, you can configure hierarchy groups and levels for a BPO, such as Acme Corp, and only users assigned to hierarchy groups under Acme Corp will be able to see or edit these users. To learn more about using agent hierarchies to enforce granular access controls for users, see the [Apply hierarchy-based access control in Amazon Connect (Preview)](./hierarchy-based-access-control.html). +In addition to tags, you can enable granular access controls for users by [configuring agent](./agent-hierarchy.html) hierarchies within the Amazon Connect admin website. Assigning hierarchies to a user allows you to define organizational groups that a user belongs to, and you can restrict users from accessing others outside their hierarchy by configure granular permissions. For example, you can configure hierarchy groups and levels for a BPO, such as Acme Corp, and only users assigned to hierarchy groups under Acme Corp will be able to see or edit these users. To learn more about using agent hierarchies to enforce granular access controls for users, see the [Apply hierarchy-based access control in Amazon Connect](./hierarchy-based-access-control.html).