9.0.0 8.3.0 8.2.0-8.2.1 8.1.0-8.1.1 8.0.0-8.0.3 7.4.0-7.4.6 7.3.0-7.3.2 7.2.0-7.2.1 7.1.0-7.1.2 7.0.0-7.0.2 6.1.0-6.1.2 View All PV Cloud PV Local Installs
Auto Light Dark
Auto Light Dark
9.0.0 8.3.0 8.2.0-8.2.1 8.1.0-8.1.1 8.0.0-8.0.3 7.4.0-7.4.6 7.3.0-7.3.2 7.2.0-7.2.1 7.1.0-7.1.2 7.0.0-7.0.2 6.1.0-6.1.2 View All PV Cloud PV Local Installs

Approvals Setup and Workflow

9.0 Admin Approvals Tab w Nav.png

When setting up Approvals for the first time, please review the information on the Approvals page to ensure a basic understanding of how Policies, Actions, and User Groups relate together in Approvals. 

Before using Approvals, there are three main items to consider:

  • User Group configuration: What users are currently under which ProVision User Groups, and what are their daily tasks?

  • Level of oversight needed: What actions should require approval?

  • Who should be involved: What users should be responsible for reviewing/approving actions, or subject to approval?

When you’re ready to proceed with setting up Approvals, continue through the steps below.

Approvals Setup and Workflow

The high level process to use when first setting up approvals is as follows:

Step 1: Review Existing User Groups and Process Needs

Step 1: Review Existing User Groups and Process Needs

Then, take a few minutes to think about the following questions to get a better sense of how to use Approvals with your specific organization:

Review User Groups and Approval Process Needs

Who are the users that perform DNS / DHCP tasks, and at what level? 

Affects which users should be included in what User Groups  

What ProVision User Group(s) are they in? 

Approvals settings are applied to the User Group, not individuals - ensure users with similar oversight needs are grouped together

What actions made by a certain user group should be automatically denied, if any? 

Assign the "Deny Action" policy to that Action/User Group combination

What actions made by a certain user group should require oversight (admin approval / rejection)? 

Assign "Submit Action" to that Action/User Group combination

Who is the admin / User Group that will make the final approval on a change? 

Ensure the approver(s) is in a User Group with the "Approve Action" policy assigned for the actions requiring approval

Should any changes require multiple admins / User Groups to approve it in order to execute? 

A single user from every group assigned with "Approve Action" for the action must approve the action for it to succeed 

If two admins are required to both  separately agree on a change, they should be under two separate User Groups assigned "Approve"

What User Groups would need to receive email Approval Status notifications, and on what type of actions? 

Affects whether to enable notifications and set up the scheduler task to send the notifications, and to what User Groups. When enabled, all users of the relevant group(s) will receive the email(s)

Once your User Groups are optimized for use with Approvals, you may want to write down a quick note on which Action Types and policies are planned for each group. 

Step 2: Add or Edit ProVision User Groups

Step 2: Add or Edit ProVision User Groups

From here, depending on the answers to the questions in step 1, you may need to do one or more of the following from the Users tab:

  1. Edit existing User Groups to add or remove users, in order to combine users who will need similar action types approved.

  2. Verify the User Groups have appropriate CRUD permissions set to perform the action(s) to be approved (e.g, you may have previously removed "Create" permissions for a group, but if the intent is now for those users to have "Add" actions approved by an Admin, the submitter will need User Group resource "Create" permissions back!)

  3. Create new User Groups specifically for use with Approvals (recommended)

  4. Associate users with different, or additional User Groups (remember - users can be associated with multiple groups!)

9.0 Approvals Scenario 1 Groups List.png


For more information on adding and editing ProVision User Groups, see Users & Permissions, Global Permissions, and Working With Users. 

Step 3: Assign Approval Action Settings to Groups

Step 3 : Assign Approval Action Settings to Groups

From the Approvals Tab, navigate to the Permission Groups sub-tab.

9.0 Approval Tab w Nav Perm Groups Groups.png

Then, under the Groups page tab, find the ProVision User Group you want to assign a policy to and click Manage Permissions.

9.0 Approvals Permission Group Scenario 1 list start.png

Clicking Manage Permissions for a group brings up a Group Assignment checklist to select which Family-Actions to apply under which policy.

Select a policy tab, then either select individual actions or "quick-select" all actions for a Family (Severs, Groups, Zones, Records) by clicking the checkbox next to the family name, or enable/disable all using the buttons at the top right. You may enter a term in the search box above the actions checklist to filter the list by keyword (such as Delete).

9.0 Approvals Group 1C Actions Submit-Deny Setup.png.png

When done, Click Save Changes and repeat as needed for other User Groups.

Step 4: Enable Notifications (Optional)

Step 4: Enable Notifications (Optional)

If using Approvals notifications, enable notifications for the appropriate Permissions Group(s).

From the Approvals Tab, navigate to the Permission Groups sub-tab Groups page tab.

8.0.0 Admin Approvals Perm Groups Circled.png

Click on the group name for which you want to set notifications - the Group Permissions Detail page will provide additional information on the group's settings.

9.0 Approvals Group Details Enable Notifications.png

For any Family/Action that you want to enable notifications, click the checkbox under "Enable Notifications". All users of that group will get email notifications when a change of the selected type(s) are made.

Step 5: Set up Approval Scheduler Tasks (Process Subscription Notifications / Delete Old Events)

Step 5: Set up Approval Scheduler Tasks

There are two Approvals-related Scheduler tasks available:

  • Approvals - Process Subscription: The "Approvals - Process Subscription" task processes approval request events and handles the sending of notification emails to subscribed Approvals Groups.

    • This task must be created, enabled, and running on a regular interval in order for Approval Notification emails to be sent.

    • it is recommended to create this to run at short, regular intervals appropriate to the needs of the users receiving the emails (every 5-10 minutes), and with no end date.

  • Approvals - Delete events older than 1 month: Set up this task to occasionally clear out old and obsolete Approval request events. This task deletes any Approvals history events older than 30 days.

    • It is recommended to set this task to run monthly with no end date, to clear out obsolete approvals items, reduce data storage space needs, and reduce approvals page load time.

To set up either of these events:

  1. Go to the Admin → Scheduler tab and click Add Task to set up the Scheduler tasks for Approvals.

9.0 Scheduler Add Approval Events.png
  1. Enter a display name for the task

  2. Click in the Task field to select the appropriate task (Approvals - Delete events older than 1 month or Approvals - Process Subscription Events)

9.0 Scheduler Approvals Process Notifications Task.png


  1. Enter a Start/End Date - We recommend leaving the end date blank in order to create as a “forever” task.

  2. Select repeat settings for the task and click Add

    1. Approvals - Delete events older than 1 month: Recommended to repeat once a month

    2. Approvals - Process subscription events: Recommended to run every 5-10 minutes

9.0 Scheduler Repeat Settings 5 minutes Add.png
  1. Click Save Task to save your task settings.

  2. 9.0 Scheduler Save Task.png

    Once the task is created, it will display in the Scheduler Task List. From here, you may view task history, view details, manually run the task now, or delete the task.

    9.0 Sceduler List Approvals Tasks.png

    For more information on setting up Scheduler Tasks, see Scheduler Tab.

Approvals - Daily Use

On a day-to-day basis after initial setup, an Approvals Workflow will be similar to the following (with "Submitter" as the user whose actions require approval, and "Approver" as the admin with the ability to approve/reject the change):

  1. Submitter makes an action (either by action type or DNS / DHCP / IPAM Family) that requires approval

  2. Submitter is notified that their action is pending approval

    7.1.0 DNS Approval Alert.png
  3. The requested change is sent to the Approvals Tab Pending Approvals list, and also to the Resources Awaiting Approval module for the relevant area (the submitter may see their own submitted action under "Resources awaiting approval", but only Approvers can take approve/reject actions).

    1. The Pending Approvals list is under the Approvals Tab. It shows Approvals events (change requests) for which the user has the ability to Approve or Deny - it does not show approval requests for all of ProVision or those for other users.

      9.0 Approvals Pending Approvals list.png


    2. A "Resources Awaiting Approval" module will display in selected DNS / DHCP pages to Users with Admin / Approval permissions, if a change has been submitted on that page that is pending approval by the User's Approval Group. 

      9.0 DNS Groups Resources Awaiting Approval.png


  4. The Approver reviews the change in either their Approvals Tab Pending Approvals list, or the Resources Awaiting Approval module, and chooses to Approve or Reject the change. Events may be approved / rejected individually, or multiple events may be selected for bulk approval / rejection by selecting the desired checkmarks, expanding the "Actions" menu, then selecting either "Approval All" or "Reject All" for the selected events.

9.0 Approvals Pending MultiSection Actions.png
    1. If Approved, and no other groups need to approve it, then the change executes and is saved. A status change notification email is sent, if enabled. 

    2. If Approved, and is waiting approval from an additional User Group, the change continues to be held as Pending, until the other group responds (Both groups must "Approve" for the change to execute). A status change notification email is sent, if enabled, stating that the change is awaiting another Group.

    3. If Rejected, the change is not executed. A status change notification email is sent, if enabled. 

Example Status Change Notification Email:

5ffe43d3-a819-4204-9c1b-5809f3db7bc6.jpeg