Config.sup file is a supervisor file that you can place company standards in and put a read only lock on. You could place it in the loadpoint text directory of ProE at the administrators level
You could now create a config.pro file for all personal setting and load that in a startup directory designated by the user by rmc on the startup icon of proE and typing in a path to the config.pro in the Start In line.
When ProE starts it reads the loadpoint/text directory first them the other startup directory. If you have a line in the config.sup and config.pro that are the same but a different setting, the line in the config.pro will override the config.sup because the config.pro was read last.
Config.pro WILL NOT override config.sup. That is the whole point of config.sup, put settings in there that you don't want anybody to be able to override. Typically, you will have relatively few settings in config.sup. One word of caution: Do not put mapkeys in config.sup. Doing so will limit you to one mapkey!
The above tells you what the config.sup file does (basically a config.pro file).The config.pro WILL NOT override the config.sup file. The last config.pro file read will override the first config.pro file read.
To create the config.sup file, start by copying a config.pro file and place it in the \text directory. For example, mine is C:\Program Files\proeWildfire 2.0\text. Then rename the file from config.pro to config.sup. Using microsoft notepad, open your new config.sup file and remove, add or change what you want all of your users to use. Make sure you use the exact directory path and the last I knew, it was case-sensative so use lower.below is one I use. I haven't really modified it for a few years but will give you an example. Also, after you make changes to the config.sup file and save, you must close and restart Pro/E for the changes to take effect.
Don't use mapkeys in a config.sup. The config.sup locks out any config entries used from being changed via config.pro. If the entry "mapkey" is used, config.sup will not let it be used via config.pro. All mapkeys will be broken.
A handy way to use the config.sup is to use a .bat in the target of your launch icon. Set this up for all your users on the local machine. Keep the config.sup on a network drive and point that b.bat file to go grab the config.sup and replace it on the local machines when pro is launched. This way you only have to keep one config.sup file update instead of going around from machine to machine making any changes. This way they can't make the changes to the sup and you only have to maintain one file. and it it's replaced with a pro start-up.