AWS connect documentation change
Summary
Updated terminology from 'third-party app' to 'integration' throughout the document, including section titles, UI labels, and references.
Security assessment
The changes are purely terminological and reflect a rebranding or feature rename (Third-party applications to Integrations). No security vulnerabilities, configurations, or features are introduced or modified. The security profile assignment step remains unchanged in substance.
Diff
diff --git a/connect/latest/adminguide/add-profileexplorer-to-agentworkspace.md b/connect/latest/adminguide/add-profileexplorer-to-agentworkspace.md index c1367a690..b09c7d01c 100644 --- a//connect/latest/adminguide/add-profileexplorer-to-agentworkspace.md +++ b//connect/latest/adminguide/add-profileexplorer-to-agentworkspace.md @@ -5 +5 @@ -Create the Profile explorer layout you want to share with agentsAdd Profile explorer to Amazon Connect as a third-party appAssign agents permission to the new security profileTell agents to pin the new applicationSupported functionality +Create the Profile explorer layout you want to share with agentsAdd Profile explorer to Amazon Connect as an integrationAssign agents permission to the new security profileTell agents to pin the new applicationSupported functionality @@ -26 +26 @@ Here's a high-level overview: -## Add Profile explorer to Amazon Connect as a third-party app +## Add Profile explorer to Amazon Connect as an integration @@ -28 +28 @@ Here's a high-level overview: - 1. On the Amazon Connect console, in the left navigation, choose **Third-party applications** , as shown in the following image. + 1. On the Amazon Connect console, in the left navigation, choose **Integrations** , as shown in the following image. @@ -30 +30 @@ Here's a high-level overview: - + @@ -32 +32 @@ Here's a high-level overview: - 2. On the **Third-party applications** page, choose **Add application**. + 2. On the **Integrations** page, choose **Add integration**. @@ -34 +34 @@ Here's a high-level overview: - 3. On the **Add application** page, complete following fields in the **Basic information** section: + 3. On the **Add integration** page, complete following fields in the **Basic information** section: @@ -38 +38 @@ Here's a high-level overview: - 2. **Application identifier** : The official name that is unique for your application. If you have only one application per access URL, we recommend that you use the origin of the access URL. You cannot change this name. + 2. **Integration identifier** : The official name that is unique for your integration. If you have only one integration per access URL, we recommend that you use the origin of the access URL. You cannot change this name. @@ -42 +42 @@ Here's a high-level overview: - 4. **Application type** : Choose **Standard application**. + 4. **Integration type** : Choose **Standard application**. @@ -50 +50 @@ The following image shows the configuration of these fields. Initialization time - + @@ -64 +64 @@ If you don't include `?_appLayoutMode=embedded`, the left navigation from the Am -For more details about what is allowed for this field, see [How to integrate a third-party application](./3p-apps.html#onboard-3p-apps-how-to-integrate). +For more details about what is allowed for this field, see [Integrations](./3p-apps.html#onboard-3p-apps-how-to-integrate). @@ -68 +68 @@ For more details about what is allowed for this field, see [How to integrate a t - 5. Completing the next two sections—**Permissions** and **Iframe configuration** —is optional and not required to add the Profile explorer to the agent workspace. For information about these sections, see [How to integrate a third-party application](./3p-apps.html#onboard-3p-apps-how-to-integrate). + 5. Completing the next two sections—**Permissions** and **Iframe configuration** —is optional and not required to add the Profile explorer to the agent workspace. For information about these sections, see [Integrations](./3p-apps.html#onboard-3p-apps-how-to-integrate). @@ -72 +72 @@ For more details about what is allowed for this field, see [How to integrate a t -You can give any instance(s) within this account-region access to this application. +You can give any instance(s) within this account-region access to this integration. @@ -74 +74 @@ You can give any instance(s) within this account-region access to this applicati - 7. Choose **Add application**. + 7. Choose **Add integration**. @@ -81 +81 @@ You can give any instance(s) within this account-region access to this applicati -In this step you need to assign agents permissions to access the new third-party application AND view permission to the Profile explorer. +In this step you need to assign agents permissions to access the new integration AND view permission to the Profile explorer. @@ -89 +89 @@ In this step you need to assign agents permissions to access the new third-party - * **Agent Applications** \- **name of your third-party app** \- **Access** + * **Agent Applications** \- **name of your integration** \- **Access** @@ -91 +91 @@ In this step you need to assign agents permissions to access the new third-party -The following image shows an example of permissions added for a new third-party application named **Profile explorer**. +The following image shows an example of permissions added for a new integration named **Profile explorer**. @@ -93 +93 @@ The following image shows an example of permissions added for a new third-party - +