https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/70863.aspxWed, 05 Oct 2011 13:30:42 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:70863cashworth0https://www.infopathdev.com:443/forums/thread/70863.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=70863<p>Hi again,</p><p>The problem I was having was a configuration issue on my end. It&#39;s working as expected now.</p><p>However, I thought that someone with the Reader permission would be able to open the list item, but not change it. The Reader permission doesn&#39;t allow the item to be opened, only show that it is there. So I was wondering whether there was anyway to have the list item be openable but not changeable.</p><p>Thanks,</p><p>Colin</p>https://www.infopathdev.com:443/forums/thread/70846.aspxTue, 04 Oct 2011 20:37:49 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:70846cashworth0https://www.infopathdev.com:443/forums/thread/70846.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=70846<p>Hi,</p><p>I currently have&nbsp;a workflow that creates tasks based on InfoPath forms that I created. The purpose for these tasks are things like approval, and confirmation requests. I was wondering how to properly restrict permissions on the task item. I currently use the CreateTask.SpecialPermissions property, but while the task&#39;s permissions say that they are what I set&nbsp;them to, a &quot;Reader&quot; can still open the form and click the approve button, thus advancing the workflow.</p><p>Any information on this would be extremely helpful.</p><p>Thanks,</p><p>Colin</p>