Sugar consists of modules, each of which represents a specific functional aspect of CRM such as Accounts, Activities, Leads, and Opportunities. For example, the Accounts module enables you to create and manage customer accounts, and the Activities module enables you to create and manage activities related to accounts, opportunities, etc. These modules are designed to help you manage customer accounts through each step of their lifecycle, starting with generating and qualifying leads to customer support and resolving reported bugs. Because many of these steps are interrelated, each module displays related information. For example, when you view the details of a particular account, the system also displays the related contacts, activities, opportunities, and bugs. You can not only view and edit this information but also create new information.
As an administrator, you have the power to implement access control for these modules. You can customize the look and feel of Sugar across your organization. You can even create new modules if needed. You can also create multiple forums as platforms of discussion on various topics amongst your users and customers.
The My Portal module allows administrators and users to link external web sites and web applications into the Sugar User Interface, enabling Sugar to become a unified information interface for its users.
Sugar is built on established open-source technologies and widely supported industry standards, including the PHP development environment, the MySQL relational database, the Apache or IIS web servers, and the Linux or Windows Server operating systems. The system supports both the LAMP (Linux, Apache, MySQL, PHP) and WIMP (Windows, IIS, MySQL, PHP) platforms.
You can create relationships between modules in Module Builder as well as Studio. In Module Builder, you can create relationships between two undeployed modules, and between one undeployed module and one deployed module. In Studio, you can create relationships only between deployed modules.
If you are managing multiple instances of the Sugar application and you want to maintain complete control over the instances, you can lock down the Upgrade Wizard to ensure that no user with administrative privileges can upgrade any of them.
In order to ensure that users with administrative privileges do not load sub-standard modules into your Sugar application, you can lock down the Module Loader and direct them to load modules from a location of your choice.