You probably want to set up "site security maintenance" in our version 36.3.13.18. You can authorize "usersid's" or better "user groups" to do transactions in a specific site. For details check manuals or on line help (F1). Let us know if this is what you are looking for.

Raymond is correct.  However, one word of caution.  As soon as you set up a site security, then that site is controlled which means that unless you specify who can have access it restricts everyone.  The best way to set this up is to create a group that matches the site code, then attach the site codes to each user that can have access.  This gives you the ability to run User group Inquiry to see which users have access to that site.  Also it makes future maintenance much easier as you don't need to change the security on the sites, just add or remove the group code from the user.  Finally, once you have Site security turned on it affects a lot of programs.  For example if you run MRP you will either need to set it up with someone who has access to all sites or users will need to enter a site range everytime they run it.

I was starting to test Phil's method but stopped until I heard back from some experts.

Thanks to Phil and Raymond for your input.

David.  I actually reread my post.  You still need to run 36.3.15 Site security but just add the group = to the Site to that as well.  For anyone with access to all sites then you might also add a group of say ALLSITE.  That way for the people who have full access you don't need to add lots of site codes to their group security.  It really depends upon how many sites you have.