> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Assignment Pools

> Group Salesforce users into a pool that workflows assign owners from, by round robin or by fewest assignments.

An assignment pool is a set of Salesforce users plus a rule for picking one of them. A workflow asks the pool for a member and sets that user as the owner. The pool itself is never stored on a record, and pools don't sync to Salesforce.

Use a pool to spread new leads across a team. Keep the routing logic, such as territory or account matching, in the workflow, and let the pool decide who on the team is next.

Pools are used by the [Assign Owner](https://docs.conversion.ai/product-docs/workflows/nodes/assign-owner.md) and [Sync Contact](https://docs.conversion.ai/product-docs/workflows/nodes/sync-contact.md) workflow nodes.

## Set up an assignment pool

Before you begin:

* Your Salesforce users must be synced. Pool members are picked from the **Users** tab of the same settings page.
* You need the Manager role or higher to create or change a pool.

1. Go to **Settings** → **Owners** → **Pools**.
2. Click **New**.
3. Enter a name, and optionally a description.
4. Choose a distribution type. See [Distribution types](#distribution-types).
5. Click **Create**.
6. On the pool page, use **Add a user...** to add each member.
7. In a workflow, add an [Assign Owner](https://docs.conversion.ai/product-docs/workflows/nodes/assign-owner.md) node, open **Assign to**, and pick the pool under **Assignment pool**.

## Distribution types

| Type | Who is picked | When a member comes back from time away |
| - | - | - |
| **Round robin** | Members take turns in the order shown in the table. | Missed turns are not made up. |
| **Fewest assignments** | The member with the fewest assignments this period, relative to their weight. | Depends on the **After time away** setting. |

One pool keeps one rotation or one set of counts, shared by every workflow that uses it. Two workflows that assign through the same pool take turns from the same list.

Changing a pool's type resets it. Every member starts over, as if no one had been assigned yet.

### Reset counts

A **Fewest assignments** pool counts each member's assignments for a period, then starts again from zero.

| Schedule | Counts return to zero |
| - | - |
| **Never** | Only when you reset the pool yourself. |
| **Weekly** | Every Monday. |
| **Monthly** | The 1st of every month. This is the default. |
| **Quarterly** | The first day of every quarter. |
| **Custom** | Every number of days, weeks, or months you choose, starting from a date you pick. |

Counts reset at the start of the day, in the time zone of whoever set the schedule.

### After time away

This setting applies to **Fewest assignments** pools and controls what happens when a paused or inactive member comes back.

| Option | Result |
| - | - |
| **Skip missed assignments** | The member rejoins level with the rest of the pool, with no backlog. This is the default. |
| **Make up missed assignments** | The member gets extra assignments until their total catches up. |

## Members

Each row in the **Members** table is one Salesforce user.

| Column | Meaning |
| - | - |
| **#** | The member's place in the order. Drag a row to move it. In a **Fewest assignments** pool the order only breaks ties. |
| **Status** | Whether the member can be picked right now. |
| **Weight** | The member's share. A weight of 2 means twice as many assignments as a weight of 1. Weights go from 1 to 10. |
| **Assigned** | Assignments this period. Shown for **Fewest assignments** pools. |

The member who will be picked next is marked **Next**.

### Member status

| Status | Meaning | Can be picked |
| - | - | - |
| **Active** | Not paused, and active in Salesforce. | Yes |
| **Paused** | Paused in this pool. | No |
| **Inactive** | The user is inactive in Salesforce. | No |
| **User removed** | The user no longer exists. | No |

Inactive users are always skipped, because Salesforce rejects inactive owners. They rejoin on their own when the user is reactivated in Salesforce.

### Edit, pause, or remove a member

Open the menu at the end of a member's row.

* **Edit** changes the member's weight and, in a **Fewest assignments** pool, their count for this period. It also holds the pause setting and an optional **Resume on** date.
* **Pause** skips the member until you resume them. **Resume** brings them back.
* **Remove** takes the member out of the pool.

Changes to a member apply to this pool only. A user can belong to several pools, and each pool keeps its own place or count for them.

Adding, removing, pausing, reordering, or reweighting a member never resets the pool. Everyone else keeps their place or count.

## Recent assignments

The **Recent assignments** table on a pool's page lists the owners the pool picked in the last 30 days, newest first: the contact, who it was assigned to, and when.

* Only owners the pool itself picked are listed. A contact that kept its current owner, or was given the fallback owner, is not.
* A new assignment can take a moment to appear.
* The **Assigned** count in the members table is what the pool uses to balance its members. It can differ from the number of rows here, for example after a count is edited by hand or a member returns from time away.

## Reset or delete a pool

Open the menu at the top right of the pool page.

* **Reset rotation** (Round robin) starts the rotation again from the first member.
* **Reset counts** (Fewest assignments) returns every member's count to zero and starts a new period.
* **Delete** removes the pool. A pool can only be deleted when no workflow assigns through it.

Resetting or deleting a pool doesn't change owners that were already assigned.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.