AWS connect documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' throughout the document, including changing references to the admin interface from 'Amazon Connect admin website' to 'Connect Customer admin website'.
Security assessment
The changes are purely branding/naming updates without modifications to security functionality. The access control mechanisms, permissions model, and security best practices remain unchanged. No vulnerabilities or security improvements are addressed.
Diff
diff --git a/connect/latest/adminguide/hierarchy-based-access-control.md b/connect/latest/adminguide/hierarchy-based-access-control.md index f718ff0fd..e2527ceef 100644 --- a//connect/latest/adminguide/hierarchy-based-access-control.md +++ b//connect/latest/adminguide/hierarchy-based-access-control.md @@ -7 +7 @@ -OverviewApply hierarchy-based access control using the API/SDKApply hierarchy-based access control using the Amazon Connect admin websiteConfiguration limitationsBest practices for applying hierarchy-based access controls +OverviewApply hierarchy-based access control using the API/SDKApply hierarchy-based access control using the Connect Customer admin websiteConfiguration limitationsBest practices for applying hierarchy-based access controls @@ -9 +9 @@ OverviewApply hierarchy-based access control using the API/SDKApply hierarchy-ba -# Apply hierarchy-based access control in Amazon Connect +# Apply hierarchy-based access control in Connect Customer @@ -21 +21 @@ This topic information about configuring hierarchy-based access controls. - * Apply hierarchy-based access control using the Amazon Connect admin website + * Apply hierarchy-based access control using the Connect Customer admin website @@ -32 +32 @@ This topic information about configuring hierarchy-based access controls. -Hierarchy-based access control enables you to configure granular access to specific resources based on the [agent hierarchy](./agent-hierarchy.html) that is assigned to a user. You can configure 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 specific resources based on the [agent hierarchy](./agent-hierarchy.html) that is assigned to a user. You can configure hierarchy-based access controls by using the API/SDK or the Connect Customer admin website. @@ -61 +61 @@ Each key represents the ID of a given hierarchy group in a specific level of the -## Apply hierarchy-based access control using the Amazon Connect admin website +## Apply hierarchy-based access control using the Connect Customer admin website @@ -63 +63 @@ Each key represents the ID of a given hierarchy group in a specific level of the -To use hierarchies to control access to resources the Amazon Connect admin website, you configure the access control section within a given security profile. +To use hierarchies to control access to resources the Connect Customer admin website, you configure the access control section within a given security profile. @@ -86 +86 @@ A user can have more than two security profiles, as long as those additional sec -Service linked roles are required in order to configure hierarchy-based access control. If your instance was created after October 2018, this is available by default with your Amazon Connect instance. However, if you have an older instance, refer to [Use service-linked roles for Amazon Connect](./connect-slr.html) for instructions for how to enable service linked roles. +Service linked roles are required in order to configure hierarchy-based access control. If your instance was created after October 2018, this is available by default with your Connect Customer instance. However, if you have an older instance, refer to [Use service-linked roles for Connect Customer](./connect-slr.html) for instructions for how to enable service linked roles. @@ -92 +92 @@ Service linked roles are required in order to configure hierarchy-based access c -Applying hierarchy-based access control is an advanced configuration feature that is supported by Amazon Connect and that follows the AWS shared responsibility model. It is important to ensure that you are correctly configuring your instance to comply with your desired authorization needs. +Applying hierarchy-based access control is an advanced configuration feature that is supported by Connect Customer and that follows the AWS shared responsibility model. It is important to ensure that you are correctly configuring your instance to comply with your desired authorization needs. @@ -102 +102 @@ For example, enabling hierarchy restricted access to users and view/edit permiss - * When logged in to the Amazon Connect console with hierarchy-based access controls applied, users will not be able to access historical change logs for the resources that they are restricted on. + * When logged in to the Connect Customer console with hierarchy-based access controls applied, users will not be able to access historical change logs for the resources that they are restricted on. @@ -110 +110 @@ For example, if you try to assign a user to a quick connect but you don't have a - * Disable access to the following functionality when you apply hierarchy-based access controls in the Amazon Connect admin website. + * Disable access to the following functionality when you apply hierarchy-based access controls in the Connect Customer admin website. @@ -122 +122 @@ Scheduling | Schedule manager - View -If you do not disable access to these resources, users with hierarchy-based access controls on a particular resource that view these pages in the Amazon Connect admin website may see an unrestricted list of users. For more information about how to manage permissions, see [List of security profile permissions](./security-profile-list.html). +If you do not disable access to these resources, users with hierarchy-based access controls on a particular resource that view these pages in the Connect Customer admin website may see an unrestricted list of users. For more information about how to manage permissions, see [List of security profile permissions](./security-profile-list.html).