About configurations and personalizations

A personalization is the same as a configuration in the system. When users make configuration changes through the Configuration Console, the changes apply to all users. This is in contrast to the changes made through the My Personalizations console, which apply only to the user making the change, unless that user has the privilege to make the change global and chooses to do so.

Configurations are saved to separate files, stored separately in the database, and are not affected by upgrades. This means when you upgrade new version of an application, any delivered changes to LPL does not override existing configurations. The LPL use depends on these conditions:

• If LPL is personalized, then the personalization is used.
• If LPL is configured, then the configuration is used.
• If there are no personalization or configurations, then the delivered LPL is used.

These are the utilities you can use:

• Review and validate all configurations within the system to see if there are conflicts between code delivered in an update and your configurations.
• Remove personalizations for Actors that have left your organization. Eliminate the need to maintain personalizations that are no longer needed.