Roles

Roles allow the administrator to manage groups of permissions granted to users. Changing permissions occurs in real-time, such that adjustments are immediate upon saving the role permissions, even if the user is already logged in. Permissions include having access to modules, and having VIEW/ADD/EDIT/DELETE permissions on module data.

Lookup Lists

All of the drop-down menus are customizable. When lists are modified over time, the values are never permanently deleted. So if there are records using a value, and that value is deleted from the drop-down, existing records will continue to show that value, but with an "*" to indicate the value is no longer current. New records will stop displaying deleted values.

Custom Folders and Fields

This capability allows for custom data to be recorded against records. Not only can you add additional fields to records, but you can add an unlimited set of custom fields to a record.

For example, in the Accounts module you might want to log the organization's Affiliate Id (a custom field), or you might want to record monthly invoices imported from another system (multiple input of custom fields).

Categories

Some capabilities in the CRM allow for hierarchical related data. In the Tickets module, for example, tickets can be categorized up to four (4) levels -- based on the selection in the first category, the second category dynamically adjusts.

Territories

Choose whether or not the "Territories" capability is right for your organization.

The introduction of territories (formerly called Sites) arose out of the corporate need to isolate groups of users and their data. The purpose of territories is to create "silos" of information among users. Users with a territory can only see data within that territory. Top-level users (those without a territory) can see data among all of the territories. These top-level users can participate within each territory and can make assignments to other territory-specific users and non-territory users. As users work within a territory, they are creating referential data which creates dependencies to the territory. Keep in mind that moving data from one territory to another is currently not possible.