Skip to main content
Nintex Community Menu Bar

Nintex Workflow Cloud - New Feature - Auto Task Delegation

  • February 18, 2026
  • 1 reply
  • 13 views

Forum|alt.badge.img+6

I wanted to make a quick post today to highlight a new feature that was released in Nintex Workflow Cloud.  The new feature is called Auto Task Delegation, this will be used for when task assignees are going on PTO, Paternity Leave, Medical Leave, etc where they will be out for a period of time and want to delegate their tasks during that time automatically.

The first thing you will need to do is make sure the feature is enabled, to do this go to your tenant settings and select Auto Task Delegation from the left-hand navigation and then make sure the feature is toggled on.

 

There is nothing that needs changed in the Assign a task action in the workflow, it will be setup like a normal task.

In order for the task assignees to setup their auto task delegation, they will sign into Nintex Workflow and click on the tasks section in My Nintex, and select the Auto Task Delegation Tab.

 

On the Auto Task Delegation Tab click the Add Auto Task Delegation button in the top right-hand corner of the page to create the new delegation.  Enter the time frame you will be out, the person you would like to delegate your tasks to during that time and a message if you wish.

 

 

Note: The user you are delegating tasks to will receive an email letting them know you have delegated your tasks to them during that time frame.  So you might want to give them a heads up before you setup the delegation.

 

And that’s all you need to do; all your tasks will be delegated to the selected user during the time frame you configured.  The settings for the delegation can be edited if you need to adjust the dates or user delegated to, as well.  Once the time frame has ended the tasks will once again be assigned to the user in the assign a task action in the workflow.

 

 

1 reply

Forum|alt.badge.img+15
  • Communicator
  • February 19, 2026

This is a great feature, and we have finally tested it. While great to have and long overdue, here are the shortcomings of this new feature:  

  1. The original task owner doesn’t see the task in their task section. I would expect it to still show up for them but with a “Delegated” status. To act the same way as “Not required” or something so they have record that it was sent to them originally. 
  2. The original task owner is not cc’d on the task that was delegated to someone when they were out. 
  3. No option to do multiple delegates. 
  4. No option to keep self on with the understanding that if a task is not set to 1st response, it could delay the any process where a task is sent.
  5. When an email comes through for a task to the delegate task owner, there should be a line in the email where the “Currently assigned to” is that has the previous owner it was original assigned to before it auto-delegated to someone else. 

Note: I get there is an initial email by the system that goes out to the delegated user and person that set up the delegation record/entry. However, that isn’t enough IMO for day-to-day operations. It really needs to be known when an email comes through who the original owner is that was assigned the task by the process that was built. We could always pass the original owner through to the email body - but we wouldn’t have a way to hide that information in the email if it wasn't applicable, so it would show up even on the original email to the original owner which is tacky.