Currently if you disable Consent and solict code under Security for certain security groups this means that users can view the consent details (but not edit them) but any solicit codes on a record are blank. This is not ideal as many of our users are infrequent users of RE and may therefore assume that a constituent has not opted in/out of any consent as the solicit codes are blank. Yes they can click on consent and try and work out from the sequential dates what the constituent has agreed to but it is not ideal. My suggestion is that Consent and Solicit codes have the same security rights as other areas i.e. view, add, edit and delete
Disabling solicit codes also seems to stop people from running queries with them in as well.
Yes. I've noticed that users can overwrite solicit codes in the webview even when the option is disabled in their security rights. That seems like an error to me.