Merge pull request #6003 from mestew/og-edit-9957939

CM-9957939-add info about default script approval settings

Author: PRMerger5

memdocs/configmgr/core/get-started/2021/includes/2110/9957939.md

@@ -9,7 +9,9 @@ ms.localizationpriority: medium
 ---
 ## <a name="bkmk_orchestration"></a> Approvals for orchestration group scripts
 <!--9957939-->
-Pre and post-scripts for [Orchestration groups](../../../../../sum/deploy-use/orchestration-groups.md) now require approval to take effect. If you open, author, or modify a script, approval for the script is required from another admin. When selecting an approved script from the [**Scripts** library](../../../../../apps/deploy-use/create-deploy-scripts.md), no additional approval is needed. To assist you with script approval, the following two tabs were added to the details pane for **Orchestration Groups**:
+Pre and post-scripts for [Orchestration groups](../../../../../sum/deploy-use/orchestration-groups.md) now require approval to take effect. If you open, author, or modify a script, approval for the script is required from another admin. When selecting an approved script from the [**Scripts** library](../../../../../apps/deploy-use/create-deploy-scripts.md), no additional approval is needed. Be default, users can't approve a script they've authored. These roles give an additional level of security against running a script without oversight. For ease of testing, you're able to [disable script approval](../../../../../apps/deploy-use/create-deploy-scripts.md#allow-users-to-approve-their-own-scripts) for the environment by changing the hierarchy setting.
+
+To assist you with script approval, the following two tabs were added to the details pane for **Orchestration Groups**:
    - **Summary**: Contains information about the selected orchestration group, including the **Approval State** of scripts.
    - **Scripts**: Lists information about pre and post-scripts, including the timeout, approver, and approval state for each script.