It makes perfect sense that you may need a configuration page for your custom SugarCRM module. Perhaps there are global settings that you need to store for your module, like credentials to connect to a 3rd-party API or key variable values. You COULD hard-code these settings into your module, but what if they change for different users? You don’t want people to have to edit code to get your module up and running. In this tutorial I’m going to show you to make an upgrade safe administration/configuration page for your module. The exercise module will store a username and password, but you can use it to store any number of values.