Inour origanziation, we do not assign "SuperUser" or "qadadmin" to staff as these roles are too broad. Instead, we defined more limited "IT" roles.
However, QAD is hard-wired to allow only SuperUser or qadadmin to access the Connection Manager. QAD Support was able to update this in response to my ticket.
They made the change through the configuration.properties which will defined which role(s) could access the connection manager.
This will also prevent any Yab or NetUI updates from overwriting the changes made. This approach required an RFC to be routed and approved.
I wanted to make others aware of this option as there are a number of "restricted" / role-specific functions / menus that could be made more flexible via this approach.
(for instance limiting IN CODE - Report Resource Designer to rptAdin or RptDgn)