Almost every step in a Chamelio flow eventually needs a person to do something — fill in a field, review a negotiation, sign a document, or approve content before it moves forward. Wherever a step needs a human in the loop, an assignment control determines who that person is. Assign Strategy lets you define a rule for how the assignee is picked, instead of hardcoding one person’s name, and Chamelio applies that rule every time the flow runs.
What “assigning” means in Chamelio
Every flow run creates a task, and that task always has an assignee — the person currently responsible for the next action. As a flow moves through its steps, the assignee can change: whoever fills out a Collect form isn’t necessarily who reviews the Negotiate step or signs the final document. Leaving a field Unassigned puts the task in a shared queue until someone claims it; setting a rule routes it automatically.
Wherever you can assign a step, the same core menu opens (a couple of options only appear where they make sense):
- Unassigned — leaves the task unowned until someone picks it up
- User Assign — hardcodes one specific teammate as the owner
- Role based assignment — routes by Owner (the task’s overall owner) or Requester (whoever submitted the intake)
- From Flow — pulls the assignee dynamically from an earlier variable
- Assign strategy — opens the smart-routing rules below
The four Assign Strategies
Where you can use Assign Strategy
Reach for Round Robin when work is interchangeable and you want fair rotation. Use Group with Default when one person should usually own the work but needs a safety net. Choose By Workload when volume is uneven. Save By Prompt for cases where the right assignee genuinely depends on the content of the request.
