Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I've created a custom approval workflow using SharePoint Designer 2007. The workflow is attached to a Forms library where InfoPath 2007 forms will be stored. The workflow is getting triggered under the user who is creating (creator) and saving the InfoPath form. I've also created a secondary workflow to manage reminders and escalations. In this case, the creator needs to be part of the site collection owners group for the workflow to complete successfully. This poses a permission issue since I am setting item level permission and granting Read permission to the creator once the form is submitted for approval. But the workflow is progressing only if the creator is given Full Control for the Forms library as well as the list item.

I've three levels of approval. Both the approvers and the creator need to have Full Control on the Tasks list and the Forms library. This also poses a permission issue to give Full Control to the approvers and creator.

Does any one know as how to impersonate the user who is part of site collection owner to trigger the work or any other work around to resolve this permission issue?

share|improve this question
add comment

3 Answers 3

SharePoint 2007 runs declarative (sharepoint designer) workflows as the user who started it.

http://blogs.msdn.com/b/sharepointdesigner/archive/2008/09/28/declarative-workflows-and-user-context.aspx

You can build a custom action to do the elevation of privileges, or use a some pre-built custom activities

http://spdactivities.codeplex.com/

SharePoint 2010 declarative workflows now have the ability to run an Impersonation Step, which runs in the context of the user that last saved the workflow.

share|improve this answer
add comment

Maybe you could consider using a custom permission level for the list. http://office.microsoft.com/en-us/windows-sharepoint-services-help/permission-levels-and-permissions-HA010100149.aspx

I would try giving add and edit items without delete & view etc. I would also suggest removing create alerts if you are promoting fields from the form that may be confidential. Disclaimer - haven't tried this myself.

share|improve this answer
add comment

maybe you can try encapsulating the code to execute the workflow with this

SPSecurity.RunWithElevatedPrivileges(delegate() { // implementation details omitted });

to read more on this method chck this link

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsecurity.runwithelevatedprivileges.aspx

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.