Skip to main content

We are in the process of changing over from InfoPath forms to Nintex forms and workflows. With InfoPath forms and SharePoint workflows users required Approve permissions to be able to approve a workflow.

According to the answer to https://community.nintex.com/thread/1611 users only require Contribute permissions to approve Nintex workflows. I believe that this is also the minimum permission required to submit a Nintex form to a list. Is there anyway to allow everyone to submit forms while still limiting who can approve Nintex workflows?

 

Nintex Forms 2010 version 1.11.3.1

 

Nintex Workflows 2010 version 2.5.1.0

Hi Paul,

what do you mean with: "Approving a workflow"? If an approval task has been assigned to someone from a Nintex Workflow, the task can already ben answered only by the assignee.

You can have a look at the presentation made by Caroline Jung‌ at InspireX: https://www.nintex.com/-/media/files/resources/events/inspirex-2017/managing-permissions-when-a-workflow-is-executing.as…  (here the link to the video of the session: https://vimeo.com/207548019 ), see the section "Permission regarding a workflow task"


Hi Giacomo

Thanks for your response. I should have said "approving a workflow task".

Anyone can submit a User Access Request Form to a list and then our Helpdesk staff have to manually start a workflow to obtain approval from one or more users. Limiting the people that could approve the InfoPath forms ensured that the Helpdesk staff didn't inadvertantly send an approval request to a personn that shouldn't be approving forms.

Nintex workflows don't seem to be able to give us that level of assurance.

Also thank you for the reference. It looks like it might take me a while to work through all the info.


Hi Paul,

if the approvers are selected by the Helpdesk, couldn't you use one or more user field set to allow people only from a specific SharePoint group where you can put all the valid approvers? You can have those fields in the start form of the approval workflow or directly as item properties (in that case, you probably have to put some extra-logic in the form in order to have those field not editable for standard users but only for helpdesk)


Hi ‌ - did Giacomo answer your question? Please mark his answer as correct if so. 


Reply