The ability to control that would have to be something exposed by the app itself. The MDM can only configure the application to behave based on what exposed configurations the app has available. Sometimes this is in the form of an external configuration file. In other cases it can be something like Managed Configurations distributed through Google Play. The host application server the device connects to can also in some cases push configuration settings to the app in use. You would need to check with Itasca or whoever develops this app to see what configuration options are exposed by the app. If its a file push, intent, or Managed Configuration you can use SOTI to apply those settings. If the app does not offer any external configurability then you won't be able to use the MDM to restrict the access. 

The answer varies with device brands/models, firmware versions, and what & how the app access Settings in the configuration process.   For some combinations, it MIGHT be able to use MobiControl application-run-control blacklist to disallow launching of certain device's Settings pages/activities.  Thorough tests have to be done to confirm that such solution do not cause any crashes of the apps or create any security/operation loophole(s).