24.1.2 updates in enterprise and classic docs (#352)

docs/en/classic/cspm-admin-guide/connect-your-cloud-platform-to-prisma-cloud/onboard-aws/onboard-aws-org.adoc

@@ -74,11 +74,7 @@ After you download the CFT from Prisma Cloud and before you upload and create a
 
 * Click *Services* from the left navigation pane.
 
-* Choose *AWS Account Management* from the list of services.
-
-* Select *Enable trusted access*.
-
-* Click *Services* again and choose *CloudFormation StackSets* from the list of services.
+* Choose *CloudFormation StackSets* from the list of services.
 
 * Select *Enable trusted access*.
 

docs/en/classic/cspm-admin-guide/connect-your-cloud-platform-to-prisma-cloud/onboard-gcp/prerequisites-to-onboard-gcp.adoc

@@ -855,7 +855,7 @@ NOTE:You must manually add the permission or update the Terraform template to en
 |Kubernetes Engine Cluster Viewer
 |`container.clusters.get`
 `container.clusters.list`
-|Project where you have created the service account
+|Every project that the service account can access
 
 |Google Cloud Translation
 |`translate.googleapis.com`

docs/en/enterprise-edition/content-collections/administration/configure-external-integrations-on-prisma-cloud/integrate-prisma-cloud-with-jira.adoc

@@ -111,4 +111,6 @@ The integration will be listed on the Integrations page.
 
 . *Next Step*
 +
-xref:../configure-external-integrations-on-prisma-cloud/add-notification-template.adoc[Add a Jira Notification Template] to configure alert notifications triggered by an alert rule to create Jira tickets.
+xref:../configure-external-integrations-on-prisma-cloud/add-notification-template.adoc[Add a Jira Notification Template] to configure alert notifications triggered by an alert rule to create Jira tickets.
+
+NOTE: If the user who set up your Jira integration is no longer with your organization, you have to follow the steps in the above two sections to create a new Jira integration.

docs/en/enterprise-edition/content-collections/alerts/send-prisma-cloud-alert-notifications-to-third-party-tools.adoc

@@ -217,6 +217,8 @@ image::alerts/alert-rule-jira.png[]
 
 . Review the *Summary* and *Save* the new alert rule or your changes to an existing alert rule.
 
+NOTE: If the user who set up your Jira integration is no longer with your organization, you have to create a new xref:../administration/configure-external-integrations-on-prisma-cloud/integrate-prisma-cloud-with-jira.adoc[Jira integration].
+
 
 [.task]
 [#idd57f95ff-7246-48c9-85d0-4eae0185b827]

docs/en/enterprise-edition/content-collections/alerts/view-respond-to-prisma-cloud-alerts.adoc

@@ -104,7 +104,11 @@ After you xref:view-respond-to-prisma-cloud-alerts.adoc#view-alerts.adoc[view al
 
 * *Investigate*—When you select an open alert for some policy types such as Config or IAM policies that use RQL, you get an automatically generated search query that enables you to review the details for the alert on *Investigate*. The ability to investigate is also available from the Alert side panel.
 
-* *Send to Jira*—When you select the Alert ID link for an alert that is in a snoozed or open state, you can send the  alert to your Jira integration. This option enables you to create and assign an action to a user and help them track status in their existing workflows.
+* *Send to Jira*—When you select the Alert ID link for an alert that is in a snoozed or open state, you can send the alert to your Jira integration. This option enables you to create and assign an action to a user and help them track status in their existing workflows. If the user who set up your Jira integration is no longer with your organization, you have to create a new xref:../administration/configure-external-integrations-on-prisma-cloud/integrate-prisma-cloud-with-jira.adoc[Jira integration].
+
+* *Send to Email*—When you select the Alert ID link for an alert that is in a snoozed or open state, you can send the alert as an email for the authorized person or team to review and remediate.
+
+* *Send to Slack*—When you select the Alert ID link for an alert that is in a snoozed or open state, you can send the alert to a Slack channel of your organization to review and remediate. 
 
 * *View in Console*—When you select the Alert ID link for an alert, the View in Console link takes you to the Cloud Service Provider console where the asset is deployed. If you have access to the CSP console, you can log in and view the details of the misconfiguration that generated the policy violation.
 
@@ -165,7 +169,13 @@ If you want to investigate further, use the *Investigate* link for the automatic
 
 .. Fix the problem.
 
-* Use *Send To Jira* to file a ticket for the application team, if you do not have the authority to fix the issue.
+* Select *Send To > Jira* to file a ticket for the application team, if you do not have the authority to fix the issue.
+* Select *Send To > Email* to enter the email address of the person or addresses (comma-separated list) of the team to whom you want to send the alert notification, add a message (optional), and *Send*. The recipient will receive an email with the alert details and remediation steps to resolve the alert (if applicable).
++
+image::alerts/send-to-email.png[]
+* Select *Send To > Slack* to enter or select the Slack channel where you want to send the alert notification, add a message (optional), and *Send*. The specified channel will receive the alert details and remediation steps to resolve the alert (if applicable).
++
+image::alerts/send-to-slack.png[]
 * Use *Fix in Cloud* to prevent an incident from occurring in runtime. Prisma Cloud can automatically execute the CLI command provided in the policy recommendations to resolve the misconfiguration.
 * Use *Fix in Code* if you have access to the IaC resource and can submit a PR to the Version Control System.
 +

docs/en/enterprise-edition/content-collections/connect/connect-cloud-accounts/onboard-aws/onboard-aws-org.adoc

@@ -76,11 +76,7 @@ After you download the CFT from Prisma Cloud and before you upload and create a
 
 * Click *Services* from the left navigation pane.
 
-* Choose *AWS Account Management* from the list of services.
-
-* Select *Enable trusted access*.
-
-* Click *Services* again and choose *CloudFormation StackSets* from the list of services.
+* Choose *CloudFormation StackSets* from the list of services.
 
 * Select *Enable trusted access*.
 

docs/en/enterprise-edition/content-collections/connect/connect-cloud-accounts/onboard-gcp/prerequisites-to-onboard-gcp.adoc

@@ -860,7 +860,7 @@ NOTE:You must manually add the permission or update the Terraform template to en
 |Kubernetes Engine Cluster Viewer
 |`container.clusters.get`
 `container.clusters.list`
-|Project where you have created the service account
+|Every project that the service account can access
 
 |Google Cloud Translation
 |`translate.googleapis.com`