To the best of my knowledge, none of the security features in the PS menu are utilized by Evo.  This is why I had just recently converted our entire office to use Evo, as it was a hodgepodge of one of the other, and difficult to administer both systems.  I still need to fine-tune our menus as well.
 
TAS-G is your key to administering the Evo menus, which I recommend modifying the default to fit all of your users, copying it for everyone, then removing particular items for each individual.  I wish that there were a way to retain the entire alphabet  by disabling the menu items like DBA does, but is in fact wishful thinking.
 
I had gotten creative with a couple logins that do not access many screens:  made only one menu level (named "menu" - instead of items, mfg, sales, etc.) and removed the letter signifying the DBA menu position (i.e. under SO, "Print Acknowledgements", "Print Packing Slips", and "Print Invoices" appear - not "B - Print...", "C - Print..." etc.).  HTH  

Quote from Lynn Pantic   on 07/13/04 at 09:27:19:

For example, if I leave the signifier (i.e. "C" for SO-C, Print Packing Slips) along with the screen title on the menu; however, want to disable a user from releasing sales orders or posting invoices, their menu (in Evo) will read A, B, C, D, F, H, I... etc.  Not a big deal, but some users get used to things being where they are, and a 26-letter alphabet.  
 
Here's a visual of what I am talking about.  I actually prefer to use a setup like the one displayed on the lower-right, as I had mentioned earlier.
 

Yeah, it seems to work well as a replacement for the structure offered by PS-B.  Using TAS-G, create a new record named _SALES (as an example - I recommend using an underscore or something for the first character to help separate groups from users as the list is sorted alphabetically) copying from DEFAULT.
 
Modify the new group accordingly, removing access from major menus like System Mgr, submenus like System Mgr - TAS, or the like... stuff that anybody in the group won't need.  When you are happy with it, save it, then create your user record (i.e. LARRY) based off of the group, and further restrict it individually by removing more menu items as necessary (i.e. maybe Larry is the overly-generous type and shouldn't be allowed to make price changes).  Save the user record when finished.  When Larry logs on, then realizes he's the only one in the sales group who can't access the price change screen, maybe he'll change his ways.  
 
Sounds like you had a good understanding of what I was getting at already.