The following describes how to activate specific debug variables for various mechanisms. Useful for developers, testers and translators. (continue)

The terminology used in LCM tries to be as neutral as possible, but this is not always possible and may be at times too confusing for some users. For example, you may wish to display “advisor” instead of “user”, “matters” instead of “cases”, etc. This is possible to do without modifying the main translation file, which is updated with new each version of LCM. (continue)

A few internal LCM features do not have a user-interface, either because they are too specific or because they are too confusing for most administrators. Such features have their default value set in “inc/inc_version.php”, but since this file should not be modified, administrators may create a “my_options.php” file where they can store site-specific configurations. (continue)

It is possible to add custom html to the login screen, as seen on the public testing site. For example, to show news or other important information to your users, before they log into the system. (continue)

Since LCM 0.7.0, it is possible to use plugins in order to add functions to validate the data entered by users into LCM, without modifying the program’s core. (continue)

By default, LCM uses the MySQL database to store the information it manages. Since LCM 0.7.0, it is now possible to use other databases, such as PostgreSQL. (continue)

The follow-ups tab of the case details shows the list of all follow-ups for that case. The list includes the follow-up date, length, user (advisor), type of activity and a short preview of the follow-up description. By default, this preview is limited to 256 characters. (continue)

In some environments, it may be confusing for users to have the «organisations» functions. Altough we did not think this was sufficiently important to implement a user-interface for this feature, it is possible to deactivate it using a «meta». (continue)