Lately I've been noticing inconsistencies when it comes to being able to start workflows or not.
I've got one case where a user should be able to start a workflow, but can't. But now I've got the opposite. A case where one user shouldn't be able to start one, but is.
The owners from either site should be able to create a document in their library starting from their list.
Now there is a third party. Their task is to edit the documents or the list items on either side. However, they should not be able to create items or start any workflows.
To do this we gave that third group of users "edit, no delete, no contribute" rights.
The funny thing is...
On one site people with those permissions CAN start a workflow, on the other one they can't. (interesting fact, we've got 31 of those sites and on 30 of them the third group can't start that workflow, but on that one site they can - My OCD can't handle it, not to mention it's unwanted behavior)
What Am I Missing?
Solved! Go to Solution.
Thank you Cassy for taking the time.
There is such an option. However, we publish such workflows from a central point so all the workflow settings are exactly the same.
First screenie is the one from the site where users are allowed to start this workflow, where they shouldn't
Second one is from one of the other sites.
We've solved it....
It's simple, but easily overlooked.
There is a task list linked to this workflow (eventho this workflow generates no tasks whatsoever!) but not having the correct permissions on this specific list makes for the weird behavior.
(not sure what permission level was needed, we solved this a few weeks ago)