Reflection for the Web loads configuration information from four sources when it starts a terminal session. These sources are listed in the order that they are loaded when Reflection runs. -items later in the list (such as user preferences and applet parameters) are loaded later and can override earlier items:
Applet and host system defaults--Default configuration values, usually embedded in the program code and inaccessible to users.
Configuration files--Component configurations, such as keyboard mapping, saved to a file by a system administrator. Within the configuration file, a system administrator can control how much customization users are able to save with user preferences.
User preferences--Customized session settings saved locally by each user. The range of configuration that the user can save is determined by the system administrator in the configuration file. For more information, go to Configuring User Preferences.
Applet parameters--Applet-based administrator settings. Parameters are loaded last and therefore have the highest priority. For a list of the parameters used in Reflection applets, see Applet Attributes and Parameters.
Using the load order you can generate different configurations for different groups in your enterprise. Create a session with a basic configuration file. Import the configuration file into new sessions; then, use applet parameters to override the basic configuration with settings customized for a specific user group.