Each eBox module status is managed from here instead of having to enable every module from one of its configuration page. This allows us to have in a single sight which modules are enabled analogously the module summary in Summary page. Each eBox module is disabled by default including base modules such as Network (Chapter 3) or Firewall (Chapter 6).

There are modules which depends on another to be enabled. In a typical installation, for example, the squid module has a chain of dependencies to be enabled as shown: squid -> firewall -> network. So to enable Squid module, firstly the dependant modules must be enabled first. A module may have multiple module dependencies to work.

The first time you enable a module, eBox will ask to perform several actions and file modifications that you must accept explicitly to enable the module. This is so to comply the Debian policy which indicate that every package must manage its own data and if it modifies configuration/data from other packages the user must accept explicitly those modifications. Every action to perform has a reason which is explained accordingly. Until you save changes, the modules that you may enable would not be committed.

Every time a user make a modification in an eBox-controlled file, eBox will realise that a change may be done when saving changes. And it will ask you again to override your changes. This monitoring is only done on those modules which are enabled. If every configuration setting is done through eBox UI, no more dialogues of this kind will be shown.

In order to disable a module, just click status column of the desired module. If the module is a dependency from other modules, this action will disable them as well.