---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Resource order controls

# Resource order controls for template-based catalog items {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Resource order controls for template-based catalog items

Resource order controls in ServiceNow Australia release enable quota management for template-based catalog items, particularly in cloud environments.
These controls help enforce limits on resource provisioning for users and groups by using quota definitions and policies.
When quota limits are exceeded, configured policy actions can trigger notifications, approval subflows, or both, ensuring controlled resource usage and governance.
Show full answer Show less  

## Key Features

* **Quota enforcement:** Allows calculation and enforcement of resource quotas for template-based catalog items, including stack count quotas across all cloud resources without requiring catalog mapping.
* **Policy-driven actions:** Supports defining policies that trigger notifications or approval workflows when resource limits are exceeded, helping maintain compliance and control.
* **Stack count quota:** Introduces a system-wide quota counting active stacks provisioned by users/groups, requiring explicit quota limits to be set for enforcement.
* **User and group visibility:** Displays quota usage for users and groups in the Cloud User portal, enabling transparency of resource consumption.

## How Resource Order Controls Work

When resource provisioning exceeds defined quotas for the first time, provisioning continues to avoid disruption. Subsequent attempts to provision resources beyond the quota will trigger the Resource Order Control policy, enforcing limits by triggering defined policy actions. Quotas must be mapped to template-based catalogs to be active; otherwise, quota checks are not performed.

## Resource Order Control Policy

The system provides a default Resource Order Control policy in draft form, which can be customized or replaced. This policy governs the behavior when resource limits are exceeded, including triggering approval subflows or notifications. Publishing the policy is necessary to enforce quota restrictions and prevent further provisioning once limits are exceeded.

## Next Steps for ServiceNow Customers

* Configure resource order controls by creating quota definitions mapped to template-based cloud catalog items.
* Define policies with rules and actions to handle quota limit breaches, such as triggering approval workflows or notifications.
* Set default quota limits for users and groups, especially to enable stack count quota enforcement.  
Use resource order controls to perform quota checks for template-based catalog items using quota definitions and policies. Quota limits enable you to control provisioning or ordering resources for users and groups. Configure
policy actions to trigger notifications, an approval subflow, or both.

## Resource Order Controls {#resource-order-control-template-based-catalog__section_ycf_k3g_mnb}

Resource order controls enable you to control the quota limit of resources provisioned
through template-based catalogs. Quota checks for cloud template-based catalog items are
available beginning with the Australia release.

You can now map quota limits to template-based catalogs and trigger notifications or an approval
subflow when the resource limit or quota definitions you specify for a user or user group is exceeded. For more information, see [Resource Quota](https://www.servicenow.com/docs/_ZO1SXbpeOKbIhlZpWRMPw "View quota limits to see how many resources you have consumed and how many you can provision based on quota limits set for you and your user group.").  
Use resource controls to perform the following actions:

* Calculate quota and capacity for template-based catalog items.
* Set limits for stack quota during provisioning for the cloud user.
* Create a policy to be triggered when a quota limit is exceeded.
* Add a policy notification and request for approval when a quota limit is exceeded.
* Show user and user group quotas for template-based catalogs in the Cloud User portal.
{#resource-order-control-template-based-catalog__ul_j4t_r3g_mnb}

## How resource order controls work {#resource-order-control-template-based-catalog__section_wkt_bxm_wnb}

Resource order control applies only when the quota has exceeded. If the quota exceeds during catalog provisioning for the first time after resource order controls are configured, the cloud resources continue to be provisioned. However, if the cloud user tries to provision a resource that breaches the configured quota limits again, the Resource order limit exceeded policy action set up for the Resource Order Control policy is triggered.  
Note:  
If quota is not mapped to a template-based catalog, quota calculations for that catalog are not performed, even if users exceed their quota limits.

For example, say you specify a quota limit of 20 GB for a storage volume for a cloud user
and the user provisions a 40 GB storage volume. The first time, the storage volume is
provisioned even though it exceeds the quota limit. However, provisioning will fail the next
time the user attempts to provision a cloud resource over 20 GB.

## Stack count quota {#resource-order-control-template-based-catalog__section_alb_vdr_tnb}

The stack count quota introduces a default base system quota for template-based cloud catalog items. The Stack count quota counts all active stacks (identified by the Stack CI class) provisioned by users and user groups. The stack count quota applies to all template-based cloud resources and you do not need to map catalog items to quota definitions. Once the stack quota is enabled, whenever a user from the group mapped to the stack quota provisions a cloud resource, the quota is calculated. When users from the mapped group try to provision resources beyond the limit defined in the quota definition for stacks, the Resource Order Control policy and on Resource Limit exceeded policy action is triggered.  
Note:  
The base system stack count quota does not have predefined default quotas to preserve stacks that might have been created prior to upgrading to Australia. You must specify default quota limits for users and user groups to enable the Stack count quota.

## Resource Order Control Policy {#resource-order-control-template-based-catalog__section_ysl_dpr_vnb}

The Resource Order Control policy is a base system policy that is in the Draft state by default. You can customize the default policy to meet your requirements and publish it, or create a new policy and define quotas, rules and actions to enable resource order controls. The 'on Resource Limits exceeded' policy action triggers the Resource Order Control policy when any resource exceeds the defined quota limit. You can determine whether to initiate an approval subflow, a notification, or a combination of both when the resource limit exceeded policy is triggered. For more information, see [Create an action for an 'on Resource Limit exceeded' policy](https://www.servicenow.com/docs/1xNNp9YqzYOcqOK_SMV43g "Set the on Resource limits exceeded policy to run approval subflows or send notifications when a template-based catalog item exceeds resource limits or quotas.").  
Note:  
You cannot provision catalog items once the user or user group quota is exceeded without the policy being published because the existing quota behavior disables further provisioning and does not process the request further.

## Next Steps {#resource-order-control-template-based-catalog__section_esv_kyw_pnb}

* **[Set up resource order controls](https://www.servicenow.com/docs/mw_hHy8~IIzZ2AwxqPlGxQ)**   
  Create quota definitions and policies mapped to cloud-template based catalog items. Use policy rules and actions to trigger an approval subflow or notification when the quota limit defined for the group or user exceeds.

