---
schema_version: "1"
id: 2acc17801287f3b59f0fcb522216b71b5e8c09a307edd5a1b52f5b35b71e0bc0
title: Attributes-Based Queues
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_attributes_based_queues_233199.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_attributes_based_queues_233199.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2395f273164024a49fc933a46ef3f14f2ce3329ce03b0d8583ac83ba20a7ea90
description: Attributes-based queues allow you to set up rules that determine how tasks are assigned.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Attributes-Based Queues

Attributes-based queues allow you to set up rules that determine how tasks are assigned.

Here's a typical workflow for creating an Attribute-Based manual queue with assignment rules:

1. A user creates a manual task and indicates a corresponding manual queue.
2. For the given manual queue, the user sets the Queue type to **Attributes-Based**. For steps about defining a manual queue, see [Configure Manual Queue Assignment Rules](https://help.salesforce.com/s/articleView?id=ind.comms_t_configure_manual_queue_assignment_rules_233255.htm&release=264.0.0&type=5 "Configure a manual queue with rules that automatically assign tasks to a specific team or user in a designated work group. This enables certain orchestration items to have priority over others, based on orchestration queue assignment rules.").
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/images/icon_note.png)
    
    Note If you don't have the option to select **Attributes-Based**, then you must add it as a picklist item. See [Update the Priority Queue Picklist Values](https://help.salesforce.com/s/articleview?id=ind.comms_update_the_priority_queue_picklist_values.htm)
3. On the same Manual queue, the user creates one or many assignment rules. Every assignment rule has a priority, with 0 being the highest priority. A condition is specified if needed.
4. For every assignment rule, the user specifies a Destination queue or Destination user. For a Destination queue, a user can repeat the previous steps because the algorithm is recursive.