Automated commit 'Merge pull request #1399 from sailpoint/devrel-719

devrel-719' by github action: 6099191319

idn/sailpoint-api.beta.yaml

@@ -736,7 +736,25 @@ tags:
 
       Refer to [Subscribe to a SOD Policy](https://documentation.sailpoint.com/saas/help/sod/policy-violations.html#subscribe-to-an-sod-policy) for more information about SOD policy subscriptions. 
   - name: SOD Violations
-    description: Operations for Predicting SOD (Seperation of Duties) violations
+    description: |
+      Use this API to check for current "separation of duties" (SOD) policy violations as well as potential future SOD policy violations. 
+      With SOD violation functionality in place, administrators can get information about current SOD policy violations and predict whether an access change will trigger new violations, which helps to prevent them from occurring at all. 
+
+      "Separation of duties" refers to the concept that people shouldn't have conflicting sets of access - all their access should be configured in a way that protects your organization's assets and data.  
+      For example, people who record monetary transactions shouldn't be able to issue payment for those transactions.
+      Any changes to major system configurations should be approved by someone other than the person requesting the change. 
+
+      Organizations can use "separation of duties" (SOD) policies to enforce and track their internal security rules throughout their tenants.
+      These SOD policies limit each user's involvement in important processes and protects the organization from individuals gaining excessive access. 
+
+      Once a SOD policy is in place, if an identity has conflicting access items, a SOD violation will trigger. 
+      These violations are included in SOD violation reports that other users will see in emails at regular intervals if they're subscribed to the SOD policy.
+      The other users can then better help to enforce these SOD policies.
+
+      Administrators can use the SOD violations APIs to check a set of identities for any current SOD violations, and they can use them to check whether adding an access item would potentially trigger a SOD violation. 
+      This second option is a good way to prevent SOD violations from triggering at all. 
+
+      Refer to [Handling Policy Violations](https://documentation.sailpoint.com/saas/help/sod/policy-violations.html) for more information about SOD policy violations. 
   - name: Sources
     description: |
       Use this API to implement and customize source functionality.