Administrators for the site, organization, and other application contexts (such as a projects, programs, products, or libraries) can set preferences for the contexts which they administer.

To access the preferences for a particular application context, click the Preference Management link on the Utilities page of that application context. The complete list of preferences for that context is displayed.

Preference values set at one level are inherited by the application contexts below. For example, preference values set at the site level are inherited by the organization; application contexts within the organization inherit preference values from the organization, as shown in the following figure:

Preference values can be set for each application context, or for an individual user, unless the preference value is locked at a higher level. For example, if a preference is not locked at the organization level, then it may have one value at the organization level, but individual products or projects within that organization could each specify a different value. Similarly, if a preference is not locked at an organization level, but is available at the user level, individual users could each set different values for that preference.

Preferences can be locked at any level above the individual user. If a preference is locked, then the value cannot be changed for any lower levels. A site or organization administrator can choose to delete all values for a particular preference that may be set at levels below the current context. These values at lower levels are known as child instances.

If a preference is not explicitly set for a particular application context, then the value for that preference is inherited from the level above. For example:

For more information on using the Preference Management utility, see Preference Management