A first step in defining your processes and customizing the system is to consider the different sets types of users who will be using the application and what kinds of the access they will need.
Users in Agiloft belong simultaneously to both groups and teams. A user can belong to multiple groups (receiving and receive the superset of those groups' permissions) , and to a primary team with additional teams. A user's access to the system – the tables and , tabs he sees, the records he sees, the and fields he sees, the records he they see, as well as records they can create and or edit , and the menu actions he they can perform - depends on group memberships. While you can It is possible to create as many groups as you need, it is preferable but from a maintenance perspective it is preferable to keep the number of groups small.
A user's primary team determines what look and feel scheme she sees they see – so you can have customers on different teams actually seeing a can see differently branded interface interfaces with different logos and colors. Staff Teams are generally used to define functional groups to whom tickets will be assigned and emails sent.
...