Hello, how can we help you?

Recent Searches: SoftExpert Survey tasks - SoftExpert Survey views - Revising a survey template - Adding a question group

SoftExpert Administration general parameters

 

 

Prerequisite

  • Access to the Configuration > General parameters (AD033) menu.

 

Introduction

The General parameters menu is used to define the default configurations of the component, which are applicable to all records created in the system. These configurations can aid in and facilitate the use of the available resources.

Furthermore, it allows you to set specific configurations that will be applied to the execution of operations while using SoftExpert Administration and other SoftExpert Suite components, such as SoftExpert Training and SoftExpert Competence.

See how to configure the general parameters of SoftExpert Administration:

 

Configuring the general parameters

1. Access the Configuration > General parameters (AD033) menu.

2. Perform the necessary configurations in each field:

Security control

In this section, it is possible to select who will be allowed to view the records referring to the employees in the SoftExpert Administration, SoftExpert Competence, and SoftExpert Training components. 

  • Control team: select the team whose members will be allowed to access the profile of all employees in the organization. The members of this team can view or edit employee profiles, as long as they have access to the corresponding menus. If this field is not filled in, the rules defined in the following fields will be applied.  
     
Allow logged user to view records from:
Their subordinates Lead users can access the profile of their subordinates. To see who the subordinates of a user are, access the Subordinate section of the user data screen.
Their peers The user will be able to access the profile of other users who have the same leader as them, or of users belonging to the same department and holding the same position, according to the configurations defined in the Peer setting section.
Their leader The user will be able to access their leader's profile. The user's leader can be identified in the Subordinate field of the user data screen.

If none of the controls are checked, the logged user will only be able to view their own data.

Employee profiles can be viewed through the View > Employee profile (AD013) menu. The logged user can view their own profile through the User panel.

To edit an employee profile, you will need permission to view the record, as well as access to the Management > Employee profile (AD006) menu.

 
 
 

Peer setting

In this section, it is possible to parameterize which users will be considered to be at the same hierarchical level as the employee during the latter's peer evaluation.

Allow logged user to view records from:
Same leader Users with the same leader will be considered as peers.
Same department/position Users belonging to the same department in the organization and holding the same position will be considered as peers.

If both parameters are checked, select the AND option in order for the system to consider as peers those users who have the same leader and the same department/position; or select the OR option in order for the system to consider as peers those users who fit into at least one of the selected options.

 
 

Feedback

In this section, it is possible to parameterize to which employees the user will be able to send feedback.

Allow the logged user to give feedback to:
Their subordinates The lead user will be able to send feedback to their subordinates. To see who a user's subordinates are, access the Subordinate section of the user data screen.
Their peers The user will be able to send feedback to other users who have the same leader as them, or to users belonging to the same department and holding the same position, according to the configurations defined in the Peer setting section.
Their leader The user will be able to send feedback to their leader. The user's leader can be identified in the Subordinate field of the user data screen.
 
 

Employee profile - Permission

In this section, it is possible to define the information that the logged user will be able to view about themselves when accessing the Employee profile screen.

The user will be able to view the available information through the General data and Career and succession tabs of the profile screen.

 
 

Employee profile - Development plan

In this section, parameterizations can be set regarding the development plans (IDPs) that may be created for the employee

  • Default category: define the category that will classify all action plans (IDPs) created for the employees. If the field is not filled in, when creating a development plan for the employee, the user can select any available category.
  • Allow changing default category: check this option so that, when creating the IDP, it is possible to change the defined default category.
  • Automation: check this field so that the system automatically cancels ongoing development plans for users who are deactivated.

Refer to the SoftExpert Action plan specific documentation for more details on configuring categories.

For this feature to work correctly, the Action plan component must be part of the solutions acquired by the organization.

 
 
 

Employee profile - Attribute

In this section, it is possible to configure the attributes that will complement the employee profile information.

  • Display in user record: the Attribute section will be displayed on the user data screen with the attributes that will be associated in this section, whether the screen is accessed from the File > Organization structure > User (AD004) menu or through the Account option in the User panel.

For more information on what attributes are and how to associate them, click here.

 
 
 

External user / Company contact - Attribute

In this section, it is possible to configure the attributes that will complement the information of external users and the contacts of companies registered in the system.

For more information on what attributes are and how to associate them, click here.

 
 
 

 

Conclusion

The parameterizations will be applied to all system records from now on!


Was this article helpful?