When you create an approval policy, you can add pre-approval and post-approval levels.

You can create multiple approval levels for an approval policy. When a service catalog user requests an item to which an approval policy with multiple levels is applied, each the first level must be accepted before the approval request is sent to the next approver. See Working with Approval Policies.

If you configure an approval policy that is triggered by a lease duration request, you must select Always Required as the approval requirement.


  1. On the Pre Approval or Post Approval tab, click the New icon (Add a level icon.).
  2. Enter a name and, optionally, a description.
  3. Select an approval requirement.



    Always Required

    The approval policy is triggered for every request.

    Required based on conditions

    The approval policy is based on one or more condition clauses.

    If you select this option, you must create the conditions. When this approval policy is applied to eligible services, catalog items, or actions in an entitlement, then the conditions are evaluated. If the conditions are true, then the request must be approved by the specified approver method before it is provisioned. If the conditions are false, then the request is provisioned without requiring an approval. For example, any requests for a virtual machine with 4 or more CPUs must be approved by the virtual infrastructure administrator.

    The availability of the fields on which to base the conditions is determined by the selected approval policy type or catalog item.

    When you enter a value for a condition, the values are case-sensitive.

    To configure more than one condition clause, select the Boolean operation for the clauses.

  4. Select the approvers.



    Specific Users and Groups

    Sends the approval request to the selected users.

    Determine approvers from the request

    Sends the approval request to the users based on the defined condition.


    Ensure that all users that will be dynamically determined by the request and requester exist in vRealize Automation, that they are synced in the Active Directory, and can be browsed from Administration > Users & Groups > Directory Users and Groups.

    If a user is not synced in the Directories Management identity provider and this user is referenced in any way during the catalog request, the request will fail with a Requested Item Approval runtime error.

    Use event subscription

    Processes the approval request based on defined event subscriptions.

    The workflow subscription must be defined in Adminstration > Events > Subcriptions. The applicable workflow subscriptions are pre-approval and post-approval.

  5. Indicate who must approve the request or action.



    Anyone can approve

    Only one of the approvers must approve before the request is processed.

    When the item is requested in the service catalog, requests for approval are sent to all approvers. If one approver approves the request, the request is approved and the request for approval is removed from the other approvers' inboxes.

    All must approve

    All of the specified approvers must approve before the request is processed.

  6. Add properties to an approval form or save the level.
    • To add properties to the approval form, click System Properties or Custom Properties.

    • To save the level, click OK.

What to do next

To add properties to the approval form, see Configure the Approval Form to Include System and Custom Properties.