No problem at all Crystal! I'm glad the explanation helped! Best of luck to you and your team and feel free to come back with more information if you run into other bumps along the way!

Hi Jarod! Now that you pointed it out this way it makes a little more sense. We originally removed security access for 95% of our users for both solicit codes and consent. As we started this process I wanted to make consent required for the 3 of us that have supervisor rights so make sure we got in the habit of using it. Since my original post there have been some updates to RE that have helped us adjust to this new function and we have a better handle on it now. It was all a little overwhelming in the beginning :) Thanks so much for pointing out this security option to make consent required for solicit codes. Now we can have the conversion around if we want to adjust the settings for some of our security groups. Thanks again! 

Hey Crystal! Thanks for submitting this. I want to point out that the reason we adding "Solicit code" permissions along with the Consent functionality was to effectively give you the power to make a Consent record "required" in order to assign or remove a Solicit Code. Is there a specific reason why utilizing this security option won't work for your use case?