🔄 Round-robin

[Bonapara]

Migrated from issue #18890, originally twentyhq/core-team-issues#2319.

Original author: @StephanieJoly4
Original issue created: 2025-10-23

Original issue body

Scope & Context

I believe there are several ways to enable this - in any case, I think this is something we will need next year.

• Twenty app
• Workflow action
• Giving access to users to the Workspace Member table + code node
  What will be needed is to add fields to the Workspace Member object to add roles for example (assume this to be a select field, with the option "seller" or "SDR") and another one, a boolean Is next assigned: t/f.
  This can theoretically be done but it's not possible (hard) to debug and test the workflow without seeing this table.

Current behavior

NA

cc @Bonapara, not urgent but curious to hear your vision on that to better answer customers. Thanks!

Migration note

The two existing issue comments were copied into this discussion as follow-up comments to preserve context.

[Bonapara]

Migrated from issue comment by @Bonapara on 2025-10-24.

It’d be a workflow node, which isn’t trivial because the node needs to share information between different runs, unlike now.

[Bonapara]

Migrated from issue comment by @StephanieJoly4 on 2025-10-24.

@Bonapara either share information between runs, either store fields like "is eligible for RR: t/f" and "lastAssignedDate" on the Workspace Member object. Then, use those fields to find the next to be assigned. (at least this is how I modeled it for a demo a few weeks ago).