AWS connect documentation change
Summary
Minor wording improvements and clarifications in tag-based access control documentation for evaluations, including pronoun adjustments and simplified phrasing.
Security assessment
Changes involve grammatical refinements (e.g., 'the users' to 'users') and clarifications about tag usage recommendations. No vulnerability fixes, security incidents, or new security features are referenced. The content discusses existing access control functionality without addressing weaknesses.
Diff
diff --git a/connect/latest/adminguide/tag-based-access-control-performance-evaluations.md b/connect/latest/adminguide/tag-based-access-control-performance-evaluations.md index 69e2a042f..d40bc0576 100644 --- a//connect/latest/adminguide/tag-based-access-control-performance-evaluations.md +++ b//connect/latest/adminguide/tag-based-access-control-performance-evaluations.md @@ -17 +17 @@ You can start by tagging evaluation forms, for example "Department: New customer - * Once you enable tag based access control on evaluations, the users will lose access to any evaluations before tagging the evaluation form. If you are already using performance evaluations, we recommend to first tag evaluation forms and accumulate evaluations over several months, before enabling tag based access to evaluations. + * Once you enable tag based access control on evaluations, users will lose access to any evaluations before tagging the evaluation form. If you are already using performance evaluations, we recommend to first tag evaluation forms and accumulate evaluations over several months, before enabling tag based access to evaluations. @@ -19 +19 @@ You can start by tagging evaluation forms, for example "Department: New customer - * It is recommended to use a single tag on an evaluation form (e.g. "Department: New customer") while configuring tag-based access. While assigning and permitting access on multiple tags is possible, it creates complexity. This is discussed in more detail below. + * We recommend using a single tag on an evaluation form (e.g. "Department: New customer") while configuring tag-based access. While assigning and permitting access on multiple tags is possible, it creates complexity. This is discussed in more detail below. @@ -87 +87 @@ Tags are copied over only to new evaluations. If you have existing evaluations, - 6. Enter the tag that you want to restrict the users' security profile to. + 6. Enter the tag that you want to use for restricting access. @@ -105 +105 @@ If you have existing evaluations, then enabling tag-based access to contact eval -If you have enabled tag-based access control on **Contact Evaluations** , it is recommended to have consistency with tag-based-access on the **Evaluation Forms**. It is also recommended that users' security profiles have access to all tags on the form(s) that they need to use. For example, if a user is to use a form with tags "Department: New customer", "Product: Auto Insurance", the security profile of the user should have access control enabled for both these tags across both **Evaluation Forms** and **Contact Evaluations**. If they have only one of the tags, then creating an evaluation manually in the UI will fail. +If you have enabled tag-based access control on **Contact Evaluations** , it is recommended to have consistency with tag-based-access on the **Evaluation Forms**. It is also recommended that users' security profiles have access to all tags on the form(s) that they need to use. For example, if a user needs to use a form with tags "Department: New customer", "Product: Auto Insurance", their security profile should have access control enabled for both these tags across both **Evaluation Forms** and **Contact Evaluations**. If they have only one of the tags, then creating an evaluation manually in the UI will fail.