Further Tasks after the Basic Configuration
- 1 User administration
- 2 Define call types to be stored
- 3 Organisation Chart
- 4 DynamicTeams
- 4.1 Preparations for the configuration of DynamicTeams for SwyxWare / NetPhone
- 4.2 Preparations for the configuration of DynamicTeams for Cisco
- 4.3 Preparations for the configuration of DynamicTeams for innovaphone
- 4.4 Particularities to consider when setting up DynamicTeams for Swyx
- 4.5 Configuration of DynamicTeams
- 4.6 Operating the DynamicTeams
- 5 Import network carrier tariff
- 6 Data protection
- 7 GDPR - General process description
- 8 Changing the WebSuite default http/https ports
- 9 Setting up additional Workstations (Administration Application)
User administration
Users can log on to the classic Windows application (or to the aurenz Web Suite, via browser) to administrate and install the aurenz software. The user-authorisations are based on a role concept were a user is assigned to a role and authorisations are assigned to the role. The user SUPERUSER is created by default and cannot be deleted or renamed. The SUPERUSER has no authorisation restrictions, and is the only user who does not belong to any role.
User
Menu bar: Setup / User
Here users can be created and managed. The creation and maintenance of these users can be done manually or automatically via LDAP or NetPhone/Swyx authentication. The settings for authentication via an external system can be found in User Authentication.
Fig. 6 - User management
The fields in the basic data area:
Name: The name is used to represent the user currently logged in. This facilitates the handling in the case of cryptic "user names".
Username: The user name is used to log in to the aurenz software.
Password: The password can be defined or changed. To comply with the four - eyes principle, a second password can be created for each user. This makes it possible, to carry out data protection-critical reports in a process-compliant manner.
Email: The email address is used for email notifications and assignments in the organisation chart.
Role: Provides the user with the authorisation level defined in the role.
Tab Choose Organisation Chart area
Three different contexts can be used to define which areas in the organisation chart the user has access to:
My company (can be optionally configured): Selecting an OU (organisation unit) authorises the user to access this and all subordinate elements.
My Team (results from the e-mail address assignment in the organisation chart): If the e-mail address of the user is entered in an organisation unit, the user is authorised to access the subordinate objects.
My data (results from the e-mail address assignment in the organisation chart): If the e-mail address of the user is entered for a subscriber/extension, the user is authorised to this object.
Tab Service Technician
If one-off costs for IT support services, are to be booked to a subscribers for example, the user can be authorised here on an organisational chart level.
Roles
Menu bar: Set up / Roles
Fig. 7 - Roles
After installation, the roles "administrators" and "standard" are available. A new user is always assigned the role "standard", further roles can be created.
A wide variety of settings can be defined for each role:
Role name
Security: minimum length, complexity and modification time interval of passwords
Granular authorisations for different program areas such as:
Reports and statistics
Menu items
Organisation chart
Data collection and telephone services
Web Suite
Call types
Data protection and tariffing
Time limits for logging in
WARNING: The role concept was introduced in version 11.2.4. Previously, these settings were maintained on a user level. When updating an older version, a role with the same name is created for each user to ensure consistent data transfer.
Define call types to be stored
Menu bar: File / Program setup / Basic settings / Call types / Storage / Communication / Call types
The aurenz software can distinguish between different call types.
Business calls (default - cannot be deactivated)
Private calls
PIN calls
Project calls
Destination number calls
Calls from provider invoice import (Business)
Carrier from provider invoice import (Private)
Deaktivate the call types you don't want to use in the reports.
Organisation Chart
In order to be able to carry out reports based on individual organisational units, e.g. department levels, you can map the company structure in the organisation chart in the form of a hierarchical tree structure in your aurenz software. Likewise, users of the aurenz software can be granted authorisation to individual or multiple levels in order to implement an authorisation concept.
Es können in bis zu sieben Hierarchieebenen erstellt werden.
Diese Ebenen können beliebige Strukturen des Unternehmens darstellen (die Einzelfirmen, Kostenstellen, Abteilungen, ...).
Im Auslieferungs-Zustand wird unter dem Knoten "Sonstiges" jeder dieser Klassifizierer dargestellt. Damit ist sichergestellt, dass alle Gespräche ausgewertet werden können. By default, each of these classifiers is shown under the "others" node. This ensures that no call data gets lost, even if the data record couldn't be assigned to an subscriber within the organisation chart.
The classifiers in "others" can be moved into the hierarchical structure by drag and drop – and a subscriber object is created from the classifier. This can be filled with further information (such as name, an e-mail address, customer, personnel number, etc.). Various classifiers can be assigned to each subscriber. Based on these classifiers, individual calls are allocated to the subscriber. A classifier could be an extension or a mobile phone number.
In this context, the "valid from" date of a subscriber node is particularly important - only calls of the classifiers from this date are assigned to the subscriber object. The older call data is displayed in a classifier object under "others" - unless there is another subscriber object with the same classifier but an earlier "valid from" date which the call data can be assigned to.
The company structure can be entered into the organisation chart like this:
Manual - create levels and subscribers by right-clicking or moving existing classifier objects with the drag & drop function.
Manual/automatic organisation chart import based on a text file
Synchronisation against an LDAP server or XIE match against HiPath Manager (only possible with certain Unify systems).
Name definitions of the organisation chart levels
Menu bar: File / Program setup / Basic settings / Organisation chart / Designations
Here you can define how the individual hierarchy levels are designated, e.g. the second hierarchy level in the delivery is called "cost centre", if you want to represent different locations of your company on this level, rename it to e.g. location. This name is used both in the organisation chart and in the reports for this level.