Welcome, I met with someone who said I should get a little more technical in my blog so based on that advice I am creating this post. I have a customer who purchased rPrograms, a CorasWorks application that sits on top of SharePoint as well as the CorasWorks Workplace suite. The customer has an existing version of Microsoft Office SharePoint Server (MOSS) Enterprise edition with the Architecture Below: This architecture is not the Microsoft recommended architecture but for the number of users they are dealing with and the scalability of MOSS they will be okay. Our requirements are to have a List where our users have the ability to view and create but not edit. SharePoint designer users the system account in Workflows but uses the permissions of the user creating and editing the item. The biggest issue here is if users outside of group A can create ad get assigned to things in this list they cannot edit these items. The challenge encountered with CorasWorks is it doesn’t like setting actions with lookup fields. I have worked around both of these issues with a simple SharePoint Designer workflow. Below is a step by step picture of the workflow: Name your workflow and select the list with the permissions set on it. Select on create and update. Eliminate the CorasWorks issue by creating a drop down choice list column and filling it with your lookup list data. From there select the condition to take the data selected in your drop down. Then create your action to insert the path of the item from your lookup list into the lookup field. See below for setting that up: Select the lookup list in source then select Path as the field. This sets the path as the inserted data, then to find the list item select the title, which is the same as the Drop Down menu, and find it by the selection of the current item’s Drop Down Value. This then fins the Title as text based in your drop down and inserts the SharePoint path (link) into the lookup field. After you have set this step for the CorasWorks work around, go onto to notifying your list members with edit rights. Get the text for your email from the customer; you can add links and other lookups to the body. The group selected has “contribute” rights to the site and have editing duties. I have created a second list in SharePoint in order to capture the assignee’s comments since they may or may not have edit rights on the original list. Here we are going to create a grab comments step that will allow this list to grab comments from another list. Now first we need to create an item on the assignee list as done below: In the Condition I ensure that it will not duplicate entries on edit by setting it not to create one if the title already appears on the list. I then tell it to create an item on the full and open permissions list. I set a 5 minute pause then an update, I also add a 1 day pause and update, and finally a 4 day pause and update. This will ensure near real time updates from the Comments list to the current list. Everytime it edits, even if by a workflow, it will restart the workflow enabling it to grab comments. I am also setting the open status when the Assigned to field is not empty, as well as sending a completion notification to the creator. I have successfully worked around my issues of CorasWorks limitations as well as SharePoint Designer Workflow limitations.