I have a workflow with an assign flexi task. When the approver clicks from the email to work the task it gives the follow "SORRY" You need edit rights to the task item to respond. The sharepoint list has the correct permissions and the workflow task list has the correct permissions. Am I missing something? I have even tried the set permission item and that doesn't help me either. I'm new and could use some help.
Have a look at this link: "You are not authorized to respond to this task." message . It contains the information on the minimum permission required to work on the task.
I hit this same limitation. It looks like what is needed is to set permissions on the "Workflow Tasks" list. Now this seems like something that Nintex should do on-the-fly. Perhaps this could be integrated into a future version?
No joy. I'm having the same problem. We're now way passed just "Contribute" rights. I've even given specific end-users Full Control on both lists (original list and task list), and even did an iisreset. They can view it, but any attempts to edit it results in the canned "sorry" message.
What am I missing?
I know this is an older post, but we recently went through a similar exercise. We found that the Nintex form was pulling in files from a resource library at the site root. The issue was the site had broken inheritance permissions and the groups were not at the top level, thus unable to read from the style library.
Using version 22.214.171.124 FYI:
Along these same lines, I too am experiencing issues with flexi-task "approvals" tasks specifically assigned to a user receiving a message stating "Sorry you are not able to view this item" (or similarly worded). They are SPECIFICALLY assigned to this task in the workflow task list and receive this message while OTHER users who are not assigned get the message "You cannot respond to this task" error message due to permissions.
Now going further, when the task is completed (either by time out or by another user) then they CAN view that EXACT same task once SharePoint releases it as complete without ANY specific permissions changes.
Its almost like instead of specifically ASSIGNING its specifically BLOCKING the assigned user (and ONLY that user) from being able to view and work with their assigned task. This to me feels like a bug and it is not working as intended.