Understand Policy Approval Workflow

What Is Policy Approval Workflow?

Scrut offers an additional feature to add extra approval layers to your policy workflow. Designated assignees or admins can add approvers even after the policy is created, ensuring a structured approval process. Once all necessary approvals are obtained, the policy can be published.

Multilevel Approval Workflow

Significant policy changes or new procedures often require multiple approvals.

For example, in a software development firm, a code deployment policy might require approval from the Quality Assurance Lead, the Chief Technology Officer, and finally the Chief Information Security Officer. The policy is published only after all approvers have given their consent, ensuring thorough endorsement from relevant stakeholders.

How to Turn On/Off Policy Approval Workflow

Follow these steps to enable or disable the policy approval workflow:

1. Click Compliance → Policies on the left navigation panel.

2. Click Settings on the top-right.

   

3. In the Configurations tab, turn on/off the Policy Approval toggle as needed.

   

When the Approval Workflow is Enabled

Here's a simplified flowchart that illustrates the policy approval workflow in this case:

When the policy approval workflow is ON, Scrut introduces an additional approval step for policies. In this step, the assigned approver reviews and approves the policy before it can be published by the admin.

When the Approval Workflow is Disabled

Here's a simplified flowchart that illustrates the policy approval workflow in this case:

When the policy approval workflow is OFF, policies do not require approval from an assigned approver before being published by the admin.