To make a new command usable for all ML's on this host, you need to put the module you wrote at /usr/local/lib/fml/site_local/ . If you permit the command is used only for the specifiec ML (e.g. elena ML), put it at the ML local library path /var/spool/ml/elena/local/lib/ where $ml_home_dir = /var/spool/ml/elena. In this section, we consider the former case. In both cases, the way of writing the module codes are same. Only path differs. Consider to make a new user command "uja". Pick up a command at FML::Command, cut and paste it. Please put it at /usr/local/lib/fml/site_local/FML/Command/User/uja.pm Edit site_default_config.cf to add it into $commands_for_user to permit the user of "uja" command. commands_for_user += uja It you allow the command only for the specific elena ML, edit /var/spool/ml/elena/config.cf in the same way. In the same way described above, hack the module!:) but the module path differs. Put it at the FML::Command::Admin:: class. For example /usr/local/lib/fml/site_local/FML/Command/Admin/uja.pm Edit site_default_config.cf to add it into $commands_for_privileged_user to permit the use of "admin uja" command. commands_for_privileged_user += uja To make a new command usable for all ML's on this host, put the module you wrote at /usr/local/lib/fml/site_local/ If you permit the command is used only for the specifiec ML (e.g. elena ML), put it at the ML local library path /var/spool/ml/elena/local/lib/ . In this section, we consider the former case. In both cases, the module codes are same. Create a module "uja" and put it at /usr/local/lib/fml/site_local/FML/Command/Admin/uja.pm You do not need to edit .cf files. The existence of module file enables the command automatically in the CUI case since the usability of CUI implies administrator use. To make a new command usable for all ML's on this host, put the module you wrote at /usr/local/lib/fml/site_local/ If you permit the command is used only for the specifiec ML (e.g. elena ML), put it at the ML local library path /var/spool/ml/elena/local/lib/ . In this section, we consider the former case. In both cases, the module codes are same. Craete a module "uja" and put it at /usr/local/lib/fml/site_local/FML/Command/Admin/uja.pm Edit site_default_config.cf to add it into $commands_for_admin_cgi to permit the use of "uja" command. commands_for_admin_cgi += uja