Do multiple Assign to user actions in a workflow stack or overwrite?
They stack. The first Assign to user action sets the primary assignee. Each later Assign to user action adds its target as a co-assignee.
How it works
When an Assign to user action runs, Plain checks whether the thread already has a primary assignee. If it does not, the target becomes the primary assignee. If it does, the target is added as a co-assignee. So the order of your actions matters.
This also applies if the thread was already assigned before the workflow ran, whether by a person or by another workflow. In that case even the first Assign to user action adds a co-assignee and leaves the existing primary assignee in place.
Each action targets one user. To add several co-assignees, add several actions in sequence.
Example: assign Ari, then a team member
A common pattern is to have Ari, your AI agent, handle the first response while the thread also lands in a team member's queue.
- Add an Assign to user action for Ari. Ari becomes the primary assignee and handles the thread.
- Add an Assign to user action for the team member. They become a co-assignee, the thread appears in their view and they receive a notification.
Co-assignees appear in thread views and receive assignment notifications. Only the primary assignee is attributed in reporting.