Merge branch 'main' into docs-1310-clean-up-index-pages

Author: jpipkin1

docs/alerts/monitors/settings.md

@@ -46,7 +46,7 @@ At the top of the page, you can:
 
 The **Monitor Details** tab provides additional information about a selected monitor, the description, Library location, [query](/docs/alerts/monitors/create-monitor/#query), [muting schedules](/docs/alerts/monitors/muting-schedules), [notification preferences](/docs/alerts/monitors/create-monitor/#step-3-notifications-optional), [alert grouping](/docs/alerts/monitors/alert-grouping), [trigger conditions](/docs/alerts/monitors/create-monitor/#step-1-set-trigger-conditions), and more.
 
-Click on any monitor in your **Monitors** table, and the **Monitor Details** tab will appear in the right-hand pane.<br/><img src={useBaseUrl('img/alerts/monitors/monitor-details.png')} alt="monitor-details.png" style={{border: '1px solid gray'}} width="600"/>
+Click on any monitor in your **Monitors** table, and the **Monitor Details** tab will appear in the right-hand pane.<br/><img src={useBaseUrl('img/alerts/monitors/monitor-details.png')} alt="monitor-details.png" style={{border: '1px solid gray'}} />
 
 ### View in Log Search
 
@@ -77,12 +77,6 @@ Click the **Disable** button put the monitor in a disabled state so it will not
 
 <img src={useBaseUrl('img/alerts/monitors/disable-monitor.png')} alt="disable-monitor" style={{border: '1px solid gray'}} width="400"/>
 
-### Mute a monitor
-
-Click the **Mute** button mute the monitor. See also: [Muting Schedules](/docs/alerts/monitors/muting-schedules).
-
-<img src={useBaseUrl('img/alerts/monitors/mute-monitor.png')} alt="mute-monitor" style={{border: '1px solid gray'}} width="400"/>
-
 ### More Actions
 
 Click the **More Actions** menu to view more options, including:
@@ -96,7 +90,7 @@ Click the **More Actions** menu to view more options, including:
    :::
 * **Copy Link**. Copies a link to the monitor. Provide the link to any Sumo Logic user in your organization so they can view the monitor. While this option doesn't allow you to share the monitor in the same way you can share a dashboard, you can use this option to quickly allow others in your Sumo Logic organization to view the monitor details.
 
-<img src={useBaseUrl('img/alerts/monitors/more-actions.png')} alt="monitor more actions" style={{border: '1px solid gray'}} width="600"/>
+<img src={useBaseUrl('img/alerts/monitors/more-actions.png')} alt="monitor more actions" style={{border: '1px solid gray'}} width="300"/>
 
 :::tip
 To quickly access this menu without opening the Details pane, just hover your mouse over a monitor, then click the three-dot kebab icon to view a menu with all of the options available in the [Monitor Details tab](#monitor-details).<br/><img src={useBaseUrl('img/alerts/monitors/quick-menu-monitors.png')} alt="Quick menu.png" style={{border: '1px solid gray'}} width="800"/>

docs/cloud-soar/automation.md

@@ -26,19 +26,44 @@ The following sections describe automation features only used in Cloud SOAR.
 
 ## Run playbooks in Cloud SOAR
 
-In Cloud SOAR, playbooks are run from [incidents](/docs/cloud-soar/incidents-triage/#incidents). To run playbooks in Cloud SOAR, perform the following steps:
-1. [Create a playbook](/docs/platform-services/automation-service/playbooks/create-playbooks/#create-a-new-playbook) to use in incident response. When you create the playbook, do the following:
-   1. Click the **Edit** icon on the **Start** node:<br/><img src={useBaseUrl('img/platform-services/automation-service/start-node.png')} alt="Start node" style={{border:'1px solid gray'}} width="100"/>
-   1. Ensure that the **Add one or more params as a playbook input** field is left blank: <br/><img src={useBaseUrl('img/platform-services/automation-service/edit-start-node-input.png')} alt="Edit node dialog" style={{border:'1px solid gray'}} width="500"/><br/>Do *not* click the field to show the dropdown menu: <br/><img src={useBaseUrl('img/platform-services/automation-service/start-node-parameters.png')} alt="Types of start node parameters" style={{border:'1px solid gray'}} width="400"/><br/>The other values in the field are used for automation outside of Cloud SOAR:
-      * **Insight** and **Entity** are for launching a playbook from a Cloud SIEM automation.
-      * **Alert** is for launching a playbook from a monitor. 
-      * **Parse from JSON** is for launching a playbook from another playbook.
-   1. Proceed to create the playbook as needed.
-1. [Create an incident template](#create-a-new-incident-template) to be assigned to incidents. When you create the template, add the playbook to the template and select **Autorun** to run the playbook when the incident is created, or deselect if you want to manually run the playbook from the incident.<br/><img src={useBaseUrl('img/cloud-soar/new-incident-template-add-playbook.png')} alt="New template" style={{border: '1px solid gray'}} width="700"/>
-1. Monitor and run playbooks on [incidents](/docs/cloud-soar/incidents-triage/#incidents):
-   * Within an incident, select **Operations > Playbooks** to see the playbooks assigned to the incident. 
-   * If playbooks haven't been assigned by an incident template, you can add playbooks by clicking the **+** button.
-   * To manually run a playbook for the incident, click the **Run** button at the bottom of the screen.<br/><img src={useBaseUrl('img/cloud-soar/playbook-on-incident.png')} alt="Playbook on an incident" style={{border: '1px solid gray'}} width="700"/>
+In Cloud SOAR, playbooks are run from [incidents](/docs/cloud-soar/incidents-triage/#incidents). This section describes how to create and run playbooks on incidents.
+
+### Create a playbook to use for incidents
+
+When you [create a playbook](/docs/platform-services/automation-service/playbooks/create-playbooks/#create-a-new-playbook) to use in incident response, do the following:
+1. Click the **Edit** icon on the **Start** node:<br/><img src={useBaseUrl('img/platform-services/automation-service/start-node.png')} alt="Start node" style={{border:'1px solid gray'}} width="100"/>
+1. Ensure that the **Add one or more params as a playbook input** field is left blank: <br/><img src={useBaseUrl('img/platform-services/automation-service/edit-start-node-input.png')} alt="Edit node dialog" style={{border:'1px solid gray'}} width="500"/><br/>Do *not* click the field to show the dropdown menu: <br/><img src={useBaseUrl('img/platform-services/automation-service/start-node-parameters.png')} alt="Types of start node parameters" style={{border:'1px solid gray'}} width="400"/><br/>The other values in the field are used for automation outside of Cloud SOAR:
+   * **Insight** and **Entity** are for launching a playbook from a Cloud SIEM automation.
+   * **Alert** is for launching a playbook from a monitor. 
+   * **Parse from JSON** is for launching a playbook from another playbook.
+1. Proceed to create the playbook as needed.
+
+### Add a playbook to an incident template
+
+1. [Create an incident template](#create-a-new-incident-template) to be assigned to incidents. 
+1. When you create the template, add the playbook to the template and select **Autorun** to run the playbook when the incident is created, or deselect if you want to manually run the playbook from the incident.<br/><img src={useBaseUrl('img/cloud-soar/new-incident-template-add-playbook.png')} alt="New template" style={{border: '1px solid gray'}} width="700"/>
+
+### Manually add a playbook to an incident
+
+1. Open the [incident](/docs/cloud-soar/incidents-triage/#incidents) in Cloud SOAR.
+1. Select **Operations > Playbooks**.
+1. Click the **+** button to add the playbook.
+1. Click **List View** to see the playbooks attached to the incident.<br/><img src={useBaseUrl('img/cloud-soar/cloud-soar-add-playbook-to-incident.png')} alt="Manually add playbook" style={{border: '1px solid gray'}} width="700"/>
+
+### Monitor and run playbooks on incidents
+
+To monitor and run playbooks on [incidents](/docs/cloud-soar/incidents-triage/#incidents):
+1. Within an incident, select **Operations > Playbooks** to see the playbooks assigned to the incident. 
+1. If playbooks haven't been assigned by an incident template, you can add playbooks by clicking the **+** button.
+1. To manually run a playbook for the incident, click the **Run** button at the bottom of the screen.<br/><img src={useBaseUrl('img/cloud-soar/playbook-on-incident.png')} alt="Playbook on an incident" style={{border: '1px solid gray'}} width="700"/>
+
+### Add a playbook to an incident with the API
+
+You can attach playbooks to an incident with the API. This lets you automate incident workflows without having to use the UI, and enables integration with external systems. 
+
+To attach one or more playbooks to an [incident](/docs/cloud-soar/incidents-triage/#incidents), with an option to auto-run them after attachment, use the [incidents_runbook_create](https://api.sumologic.com/docs/csoar/#operation/incidents_runbook_create) API. To retrieve all playbooks attached to a specific incident, use the [incidents_runbook_retrieve](https://api.sumologic.com/docs/csoar/#operation/incidents_runbook_retrieve) API.
+
+For more information about how to use APIs, see [Cloud SOAR APIs](/docs/api/cloud-soar/).
 
 ## Incident templates
 

docs/cloud-soar/incidents-triage.md

@@ -269,7 +269,7 @@ All the information related to the ongoing incident is  visible in one place in
 
 #### Playbooks
 
-Any playbook that has been applied to an incident can be found under the **Playbooks** section. You can quickly view and make any necessary adjustments to the incident's playbooks, as well as add any additional playbooks that may be required during an incident's investigation.
+Any playbook that has been applied to an incident can be found under the **Playbooks** section. You can quickly view and make any necessary adjustments to the incident's playbooks, as well as add any additional playbooks that may be required during an incident's investigation. For more information, see [Run playbooks in Cloud SOAR](/docs/cloud-soar/automation/#run-playbooks-in-cloud-soar).
 
 <img src={useBaseUrl('img/cloud-soar/operations-playbooks-tab.png')} alt="Playbooks displayed in the Playbooks tab" style={{border: '1px solid gray'}} width="700"/>
 

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/smartsheet-source.md

@@ -24,7 +24,9 @@ Smartsheet is used to collaborate on project timelines, documents, calendars, ta
 
 ### Vendor configuration
 
-To collect data from Smartsheet, you need a Smartsheet account with admin privileges that would allow the creation of an app via a developer account. See [steps in the Smartsheet documentation](https://smartsheet.redoc.ly/#section/OAuth-Walkthrough/First-Steps) to create a developer account in Smartsheet.
+To collect data from Smartsheet, you must have a Smartsheet account with **Admin** privileges, which allows you to create an app using a developer account. Refer to the [Smartsheet documentation](https://smartsheet.redoc.ly/#section/OAuth-Walkthrough/First-Steps) for the steps to create a developer account.
+
+To collect data from the `\events` endpoint, the Event Reporting **Premium add-on** is required. This add-on is available for **Enterprise and Advanced Work Management** plans, and you must have **System Admin** permissions. Refer to the [Smartsheet documentation](https://developers.smartsheet.com/api/smartsheet/openapi/events/list-events) for more details. You can also contact Smartsheet support to enable this permission for your account.
 
 ### Source configuration
 

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/workday-source.md

@@ -44,7 +44,7 @@ This section demonstrates how to configure the Workday portal to integrate with
 1. To register the API client, access the **Register API Client** **for Integrations** task, and provide the following parameters:
     * **Client Name.** Sumo Logic Workday Collector
     * **Non-Expiring Refresh Tokens.** Yes
-    * **Scope.** System
+    * **Scope.** System, Integration, and Tenant Non-Configurable scopes are *required*.
 2. Click **OK**.
 3. Copy the **Client Secret** and **Client ID** before you navigate away from the page and store it securely. If you lose the **Client Secret**, you can generate a new one using the **Generate New API Client Secret** task.
 4. Click **Done**.