I tried posting this as a reply above, but it has been stuck in moderation for 2 days now. I'll try here instead. 

Hi Caitlin (and team),

I'd like to encourage your team to not give up. I respectfully reject your assertions that this isn't possible. I know this is in fact possible, as I've seen it working (with other applications and with your application when signed). Your team unfortunately did not research extensively enough.  While I agree signing the application in and of itself not enough, if you have an Apple MDM setup and deploy your own privacy policy that whitelists the application (a signed application is required), then you can remotely approve the use of CW Control *without* any user intervention on the first connection. Let me try to help by providing some reading material:

https://derflounder.wordpress.com/2018/08/31/creating-privacy-preferences-policy-control-profiles-for-macos/

https://www.jamf.com/jamf-nation/articles/553/preparing-your-organization-for-user-data-protections-on-macos-10-14

https://macadmins.herokuapp.com/ (see mdm channel)

https://github.com/carlashley/tccprofile

I'd love to work with you and your team more directly to make sure this comes to light. If that is at all helpful, please don't hesitate to contact me. Here are the signing requests:

https://control.product.connectwise.com/communities/6/topics/1974-complicated-process-required-to-control-macos-1014-mojave-clients

https://control.product.connectwise.com/communities/6/topics/2014-mac-signed-application

Please note, this is the .app that needs to be signed, not the installer. 

Thank you for considering my feedback on this.

https://control.product.connectwise.com/communities/6/topics/1974-complicated-process-required-to-control-macos-1014-mojave-clients

I just did a fresh install of 6.9.20424.6863 and tried to setup a Privacy Preferences Policy Control whitelist payload, but the /opt/screenconnect-XXXXXXXXXX.app is still coming back as not signed. Here's what I'm seeing:

$ codesign -dv /opt/screenconnect-XXXXXXXXXX.app/
/opt/screenconnect-XXXXXXXXXX.app/: code object is not signed at all

vs:

$ codesign -dv /Applications/iTerm.app
Executable=/Applications/iTerm.app/Contents/MacOS/iTerm2
Identifier=com.googlecode.iterm2
Format=app bundle with Mach-O thin (x86_64)
CodeDirectory v=20200 size=79381 flags=0x0(none) hashes=2473+5 location=embedded
Signature size=4620
Signed Time=Nov 11, 2018 at 2:49:13 PM
Info.plist entries=47
TeamIdentifier=H7V7XYVQ7D
Sealed Resources version=2 rules=13 files=153
Internal requirements count=1 size=216

In other words, suggesting I install a browser extension doesn't fulfill my request.

That doesn't help when I have other users involved. I'm requesting this both for security auditing and troubleshooting with users that I can't install browser add-ons for. I was told in Ticket #11121108 to create a feature request. Here we are...

I agree something native would be great. HTML5 client might also be a way to accomplish this. (Update: I found this https://control.product.connectwise.com/communities/1/topics/369-html5-client)