A Unit represents a body of Users which belong to the same team and follow the same business processes; Users belong to Units.

Organisational Units are used to organise the company’s network and define the collaboration between them (between whom? between Units?). Communities, Groups and Units are all CRM.COM Organisational Units.

In case a company consists of multiple organisations (i.e. multiple databases), the organisations can be grouped under a single Group.

Super Users are authorised to access all areas and features of the software, including unrestricted access to Network Management and Security Management. A Super User can only be appointed by another Super User.

Super Users can also view more detailed error messages than the rest of the Users.

Users with access to the development tools embedded in CRM.COM, and which are available in all Summary pages, Data Entry pages, Analytics and Dashboards. Developers are granted the same permissions as normal Users as far as Network Management and Security Management restrictions are concerned. A developer can only be appointed by a Super User. 

• Phone extension: Determines the extension number of the phone device installed on the User's PC, through which the User accesses CRM.COM. As this setting is found under the User Settings section, it can only be edited by Super Users.

Defines whether a User is 'Active' or 'Inactive'. 'Active' Users can access the System and can be used for assignment in various entities of the software. 'Inactive' Users cannot access the System or be used for assignments. 

Information about previously 'Active' System Users which are now 'Inactive' is available to Users.

Active Directory (AD) is a directory service that Microsoft developed for Windows domain networks and is included in most Windows Server Operating Systems as a set of processes and services.  

An AD domain controller authenticates and authorises all Users and computers in a Windows domain type network—assigning and enforcing security policies and installing or updating software. For example, when a User logs into a computer that is part of a Windows domain, Active Directory checks the submitted password and determines whether the User is a system administrator or a normal User.  

Active Directory makes use of Lightweight Directory Access Protocol (LDAP) versions 2 and 3, Microsoft's version of Kerberos, and DNS.

A Template within CRM.COM is used to reduce repetitive manual work. A User Template is used to create multiple Users in the System with the same characteristics. The data that is common between all Users can be added on a Template, leaving only unique values for Users to complete.

A User can be assigned to multiple Units.
Network Management defines the access to data of each Group that a Unit belongs to; therefore, Users have access to the data allowed to be used by the Group their Unit belongs to. In case a User belongs to multiple Units, the sign-in Unit must be selected when logging into the System, so as to define the access level based on the Unit. Users that are already logged in the System and belong to multiple Units, can change Unit by selecting the SWITCH UNIT button available at the Top Menu Bar.

• Super Users are authorised to access all areas and features of the software. Network Management and Security Management restrictions are not applicable to Super Users. A Super User can only be appointed by another Super User.
  • Super Users can also view more detailed error messages than the rest of the Users.
• Developers are Users with access to the development tools embedded in CRM.COM, and which are available in all Summary pages, Data Entry pages, Analytics and Dashboards. Developers are granted the same permissions as normal Users as far as Network Management and Security Management restrictions are concerned. A developer can only be appointed by a Super User.

The User Information Panel (available under ACCOUNT via the CRM.COM Top Menu Bar) displays the Unit and Group of the User and provides access to the User Data Entry page (to change User information).

In case the password needs to be updated, the User will be required to enter both the previous and the new password. If the password change is executed by a Super User, the previous password is not required.

• The User can define a different System and Native language.
  • The System language is used to select the language that will be used to translate all labels, tips, warnings and error messages across the CRM.COM software, including the values of select boxes, radio buttons and other elements which consist of fixed (not configurable) values.
  • The Native language is used to select the language that will be used to translate additional information for each label across the CRM.COM software. This additional information is displayed when the mouse is placed over a specific label.

Already established organisations (with hundreds of Users) which are using Microsoft's Active Directory (See Glossary above) have the option to import their registered Users from Active Directory directly to CRM.COM and map them to CRM.COM User accounts. Mapping Active Directory User accounts to CRM.COM accounts, provides the options to:

• Authenticate Users during login to CRM.COM, using their Active Directory accounts.
• Inform Users about their Active Directory password expiration.
• Prevent User login once the User's Active Directory password expires.

IP Authorisation Rules are used to define IP addresses from which Users can access CRM.COM or IP addresses from which Users cannot access CRM.COM. Each IP Authorisation Rule contains a set of restrictions representing the Allowed and Denied IP Addresses. An IP Address restriction can either be a specific IP address, a range of IP Addresses or an IP Address Pattern. Each IP Authorisation Rule also contains a set of conditions which define the set of Users to which the rule applies. This set of conditions includes Users, Units, Groups or Communities in any required combination. Multiple IP Authorisation Rules can be configured and used as long as they are in 'Active' state.

A User Password can be set as 'Valid' for a limited period. If a password is expiring in the next seven days, the System informs the Users about the number of days left upon login. The same password can never be selected by the same User.

• Entities with Exceptional Viewing Access

• Viewed by Users which are accessing the System using a Unit that belongs to the same Group as one of the Units that the User belongs to
• Viewed by Users who are accessing the System using a Unit that belongs to a Group that collaborates with the Group that includes one of the units, that the User belongs to (considering that the share my Units is selected)
• Viewed by Super Users

• Global Viewing Access

• User Templates have no access restrictions. They can be viewed and selected by all Users.

User access rights in the System are assigned through the Units the Users belong to.