I believe this is a catch 22 but would like to know if there is a way around this.
I have created a owrkflow which copies an entry from one list to another, then deletes the entry in the original list. I originally gave Contribute the the Authenticated Users group on the first list - to allow them to create tickets, and Read access on the second list. Of course the workflow failed since they require Contribute on the second list to achieve this. I then used an impersonation step to run the step of copying the entry to the second list - this works fine ! The problem now is that the e-mail which is sent back to the Creator as part of the Workflow, is now attempting to send to the account under which the Impersonation is running - the Workflow Designer, instead of the Creator. I can work round this by removing the impersonation step, and giving Contributor to the Authenticated users on the second list, but they are then able to UPDATE tickets in the second list - NOT what is required.
Does anyone have an alternative way of doing this - it seems as if the Creator is being overwritten to show the account under which the Impersonation is run - and thus when the step to email the creator is run, it sees the creator as the impersonation account ?
Thanks to all who assist