Hi Barb, that may not be possible.  Record level security on CM Bank accounts only affects what users can see on Reports and inquiries and doesn't prevent them from access to the banks in tasks they have permission to access in CM (Such as Setup bank accounts and Edit register)

So what does everyone else do with their payroll checking accounts to prevent someone with CM Edit Eegister access (legitimitely needed for other non-payroll accounts) from opening this payroll account and looking at the transactions? I must be missing something?! 

Often it is necessary for security purposes to keep some files stored in separate folders that point back to another folder in the file locations.  For example you could have a separate PR company folder that has the PR and CM files (and just the banks that PR uses in CM) in one folder and point back to you main company folder for the GL, JC, etc. etc files.  You may want to reach out to your consultant to have a look at the big picture to determine the best way to accomplish what you need to happen here.  Otherwise just don't give access to anything other than reports and inquiries in CM to users that should not be able to make entries and/or change settings in all banks. (as Record level security would prevent them from seeing information associated with Banks they do not have permission to view)

Thanks for confirming what I suspected was the case, that it is NOT possible to restrict just one account from Edit Register without jumping through a bunch of hoops and moving files and data folders. I did look to submit an enhancement request, and there are already several existing requests for the same thing from "over a year ago". Does anyone actually look at these requests, or is it just a place to send someone when Sage knows there's a problem, and they don't want to be bothered with fixing it?

Our developers do look at the submitted enhancement requests.  Each needs to be prioritized and evaluated based on risk and reward.  Enhancements are a lower priority over government mandated changes and defects, so many enhancements are slow to be included in a release, if ever at all (based on risk and reward). The CM Record level security is working as designed so it's not broken.   Sometimes adding an enhancment feature that wasn't included in the original design causes other things to break. It's a very complicated process to determine what enhancements we can add and still be able to get releases out in a timely manner.