---
schema_version: "1"
id: a67f230f1f35082c8d313ec38e5f72e2e74e93e542826893e26a84efb664b3e1
title: How Assignment Rules Work for IT Services
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/it_srvcs_assignment_rules_explainer.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.it_srvcs_assignment_rules_explainer.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 91c5865a223162392bad44cffe3fa0a3c43bcc118403a2ae422da5532d3314e0
description: Assignment rules use a record’s attributes for defining the criteria for distribution. You can configure a rule to assign the record to a user or a queue.
products:
  - Service Cloud
  - Agentforce IT Service
release: "264"
---
# How Assignment Rules Work for IT Services

Assignment rules use a record’s attributes for defining the criteria for distribution. You can configure a rule to assign the record to a user or a queue.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions with Agentforce IT Service.</td></tr></tbody></table>

When a record, such as an incident, is created, the associated assignment rule is triggered. Salesforce checks the record's details, such as priority and category, against the rule's conditions. If a match is found, the rule automatically assigns the record to the defined user or queue.

If the assignment rule assigns the record directly to a user, the record is assigned to that user. If the assignment rule assigns the record to a queue, the record remains in the queue until it's routed or assigned to a support representative.

That’s where Omnichannel routing comes in. Omnichannel routing and assignment rules complement each other and reduce manual effort.

If you set up Omnichannel routing, Omnichannel routes record assigned to a queue (Owner = Queue) to the most suitable support representative based on your routing model. Assign records to queues so Omnichannel can route them.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-it_service-264-0-0-production-enus/0a574a10-4c7a-4681-aacf-0767f8beaad4/images/icon_note.png)

Note

You can create assignment rules for incidents, problems, change requests, releases, and service requests. Omnichannel routing isn't available for releases and service requests.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-it_service-264-0-0-production-enus/0a574a10-4c7a-4681-aacf-0767f8beaad4/images/icon_example.png)

Example

Some examples of assignment rules include:

- Incident with category = Network and subcategory = VPN is auto-assigned to the Network Support team
- P1 outage incidents are autoassigned to the Critical Incident Response team
- Problem record tagged as recurring for a specific app is routed to the App Support L2 team
- Incident with priority = High is autoassigned to the on-call support representative