---
schema_version: "1"
id: bd89112d5a5258fed769b0341858bd654696e4ebc60798216ec95f7fba5ade8f
title: Considerations for Multi-Resource Scheduling
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/service-cloud/salesforce-scheduler-dev-guide/guides/salesforce-scheduler/uc3-considerations-for-multi-resource-appointment.md
canonical_url: https://developer.salesforce.com/docs/service/salesforce-scheduler-dev-guide/guide/uc3-considerations-for-multi-resource-appointment.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 5cecb40a24e0d23bc613199cd8fab6a968ac389647ffb58d03a9138c089d77c3
products:
  - Salesforce Scheduler Developer Guide
  - Service Cloud Developer Content
---

# Considerations for Multi-Resource Scheduling

In multi-resource scheduling, a primary service resource anchors the appointment and must be marked required. Primary service resources are the only required resources whose skills are matched to the skill requirements for an appointment. Other required service resources are matched to appointments based on their availability and the primary resource’s service territory.

Here’s how matching is done for different types of service resources when multi-resource scheduling is enabled.

|Matches On|Primary Service Resource|Required Service Resource|
|----------|------------------------|-------------------------|
|Skill Requirements|Yes|No|
|Service Territory|Yes|Yes|
|Availability in Time Slots|Yes|Yes|