Hi, @hassang,
Yes, it is correct I tried it with another new instance, but it remains the same.
In a few minutes I will share what I have configured in Camunda Admin.
Here are my users for my tests create user1 and user2.}
both users belong to the group “com”
In “Authorizations” assign all groups with all permissions for Tasklist.
In “Authorization” assign the groups with Read and Update permissions, (As the TASK_WORK did not work for me I created the authorization for user1 and user2 in this section.)
In “Filter” all my groups have read and update permissions.
In “Process Definition”, create the authorizations for my groups, user1 and user2, they belong to the main group that starts an instance and the other groups cannot start a new instance due to the tasks that each group must perform.
In “Process instance” the group “with” select all permissions, so that any member of this group can start instances.
@hassang
This is all I have done.
I’m doing something wrong, because even with all this configuration, if the task has already been claimed by user X and this user is performing the task, and another user logs in that belongs to the same group as user X, it displays the task and resets the user and claims the task everything done by any other user will lose their work.
@hassang WHAT I WANT TO ACHIEVE IS TO DEFINITELY BLOCK THE TASKS THAT WERE ALREADY CLAIMED BY X USER, IT DOES NOT MATTER IF THE OTHER USER BELONGS TO THE SAME WORK GROUP, THAT THE USER CANNOT RESET AND CANNOT CLAIM THE PREVIOUS TASK.