--- title: "Approve security request" slug: "approve-security-request" description: "Learn how to approve security requests, manage workflows, and handle conflicts effectively in your security management process." tags: ["Task", "Security and Compliance Studio", "SCS"] updated: 2026-07-10T06:28:31Z published: 2026-07-10T06:28:31Z canonical: "docs.staedean.com/approve-security-request" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Approve security request Usually, a security manager must approve the security request before it is implemented. How the approval process is done depends on the setup: - An approval workflow is active: Approve the security request using the approval workflow. - No approval workflow is active: Manually approve the security request. When you review the security request, on the **Security requests** page, on the Action Pane, on the **Requests** tab, you can: - View the related record, if defined. - Change the priority. Once approved, the security request is implemented automatically. If dynamic snapshots are enabled, the implemented security configuration changes are updated automatically in the latest snapshot. ### Steps 1. Click **Security management**. 2. On the **Requests** tab, in the list, click the link of the desired security request. 3. Sub-task: Approve using approval workflow. 1. Click **Workflow**. 2. Click the desired action that defines the next workflow step and status. For example, click **Approve**. 3. On the dialog, in the **Enter a comment** field, type a value. 4. Click **OK**. > [!NOTE] > Note > > On approval, a segregation of duties (enhanced) validation is done. If a conflict is found, the request is not approved. Depending on the workflow setup, the request status is set to '**Change request**' or '**Cancelled**'. To continue with the request, resolve the conflict. 4. Sub-task: Approve manually. 1. To indicate that the approval of the security request has started, set the status to **Review**. Click **Status**. 2. Click **Review**. 3. When you have finished the approval of the security request, indicate the approval outcome. Click **Status**. 4. Click the desired status, for example, **Approved**. > [!NOTE] > Note > > - If you need, for example, additional information on the security request, you can reject or re-open it. Also, change the ownership to the **Created by user**. The **Created by user** can make changes to the security request only if the status is **Open** or **Rejected**. > - On approval, a segregation of duties (enhanced) validation is done. If a conflict is found, the request is not approved. To continue with the request, resolve the conflict. 5. Close the page. ### From/to date For several security request types, you can set a **From date** and **To date** to define the period when the requested security setup change is valid. When the request is approved: - If the defined period starts in the future, the **Implement approved security requests** batch job applies the change on the **From date**. - If the defined period has already started, the change is applied immediately. The **Implement approved security requests** batch job undoes the change on the **To date**. > [!NOTE] > Note > > The **Implement approved security requests** batch job is configured and started automatically when you install Security and Compliance Studio. ### Notification email If you approve a security request of type ‘**Assign role to user**’, and the assigned role gives access to sensitive data, a notification email is sent based on the **Sensitive role notification** setup. The email is sent to the relevant user and, if defined, to other users as well. > [!NOTE] > Note > > If no applicable notification setup exists, no email is sent. ## Related - [Resolve segregation of duties conflicts (enhanced)](/resolve-segregation-of-duties-conflicts-enhanced.md) - [Set up email notification for sensitive data role assignments](/set-up-email-notification-for-sensitive-data-role-assignments.md)