views:

1458

answers:

2

Hello, I've created a custom workflow using Visual Studio 08 that uses a custom content type and .aspx task edit form. The tasks are successfully created and assigned to the users. However, only users that are members of the Site Owners group are able to 'Edit' the task items. All others (even though they have contribute and approve permissions) cannot browse to the custom task edit form in the _layouts directory but instead receive the standard "Access Denied" page. The task list's item-level permissions are also set to allow users to read and edit all items not just their own, yet it still doesn't work.

Giving these users Site Owner permissions in order to be able to edit their tasks is not an option for us. Is there any solution or workaround to this issue?

Any help would be greatly appreciated.

A: 

I would say go to Site Settings>Advanced Permissions>Permission Levels, click on the Contribute permission level and view its settings - maybe someone unchecked a List or Site Permission?

Users with Read permissions should be able to view custom forms in the /_layouts/ folder. I would also check the file permissions in the 12 hive just in case.

Ajay Nayak
Thanks for your reply, Ajay. I verified that the Contribute permission level is as expected. I even created a new permission level with all the settings copied from the Full Control permission level, then applied that permission level to the user group for the task list only (though this is still highly undersirable) just to see what it would do, and still nothing. Weird huh? I also checked the ACL permissions on the layouts folder. Tried giving the Everyone group full control (again just to see where that took me) but nothing. Any other ideas are appreciated.
Can you access the workflow form in a different site collection or web app as a member? Check how widespread this problem is.
Ajay Nayak
The workflow form requires certain query parameters (e.g., the task list id) which won't be found in a different site collection. Not sure how I could test for that...
For a different site collection on the same web app, just create a task using your custom workflow and open the task.For a different web app, deploy your custom workflow to this web app, then create a new site collection and do the above.
Ajay Nayak
I see what you mean. Well I have deployed the workflow to two different servers with the same results.
Ajay, It seems that at a minimum users must have Design permissions at the subsite level in order to be able to edit workflow tasks or start workflows. (http://social.msdn.microsoft.com/Forums/en-US/sharepointworkflow/thread/1f1df076-ae72-4a63-8f0f-485a8e74c291). This is not ideal. If this is inconsistent with what you've found, please let me know. Thanks...
A: 

If you're using any SharePoint Designer workflows, this could be the problem: http://www.binarywave.com/blogs/eshupps/Lists/Posts/Post.aspx?List=9c93c708-e5ce-4714-bdea-499330361130&ID=160

Dave

related questions