Defining the roles, permissions and memberships of QAD users and assigning their access security can be challenging and complex, especially if your company needs to be SOX compliant. Don Lindsey’s walk-through of the essential considerations when assigning roles, permissions, and security in QAD will help! You’ll learn about:
• Sarbanes-Oxley compliance considerations
• Access security control
• User setup
• Menus and menu maintenance
• Roles, permissions and memberships
• And, more
If I have a new user and only want that user to have 3 menu options for his/her job, can I assign menu options without applying a role?
If you are using SE, you can assign a user to a menu.
If you are using EE, I do not know of any way in EE to give a user access to a single menu option other than creating a Role = Menu. For example,
Role = 7.1.1. From the EE Help: Role Name, Enter a name (maximum 20 characters) identifying a role. Names are restricted to the characters A-Z, a-z, and 0-9.
If I create a new browse, is there a quick way to add that browse to all the roles that I want to add it to, other than going to each role and checking/saving?
I don’t know of any way other than to assign that menu to a role through 36.3.6.5 – Role Permissions Maintain. You can utilize 36.3.6.11 – Role Export and 36.3.6.12 – Role Import, but that is cumbersome and if you have never used 36.3.11 and 36.3.6.12 it can be confusing. Otherwise, the process of updating each role, checking and saving, as you indicate, is probably the best way to assure you get the new menu assigned correctly.
Can you tell the attendees about the QAD mfg logon? Where I work, they did not understand this when they implemented and have given “regular” users the mfg logon name access. Should this not only be used in scripts, etc.
It is never a good idea to give the ID: mfg and password to regular users. You could just change the mfg password, but you can run into troubles even with that as mfg can be used in several ways in QAD, from Cron file settings to Linux settings. Sometimes we have seen the mfg password hardcoded into the system. “Mfg” is used in some batch scripts and the password has to be provided (saved in some input files) to connect and run other the programs.
Correction of such as action from the past could require a fair amount of research and testing to take mgf/password away from users.
Join our mailing list to stay informed about our webinars
