Approval policies are governance that you add to service catalog requests so that you can manage resources in your environment. Each policy is a defined set of conditions that can be applied to services, catalog items, and actions when you entitle users to those items.

Approval Policy Process

First, a tenant administrator or approval administrator creates the approval policies where provisioning governance is needed.

Approval policies are created for approval policy types or specific items. If the policy is based on a policy type, you can apply it to matching catalog item types. For example, if a policy is based on a software policy type, then you can define it for and apply it to any software items in the entitlements. If the policy is for a specific item, you should apply it only to that item. For example, if the item is a specific software item, then you should apply it only to that specific database software item in the entitlement.

Policies can include pre-approval and post-approval requirements. For pre approval, the request must be approved before the requested item is provisioned. Post approval policies require that the approver accept the request before the provisioned item is made available to the requesting user.

The pre and post approval configurations are composed of one or more levels that determine when the approval policy is triggered and who or how the request is approved. You can include multiple levels. For example, an approval policy can have one level for manager approval, followed by a level for finance approval.

Next, a tenant administrator or business group manager applies the approval policies to the services, catalog items, and actions as appropriate.

Finally, when a service catalog user requests an item to which an approval policy is applied, the approvers approve or reject the request on their Inbox tab. The requesting user can track the approval status for a specific request on their Deployments tab.