The settings in the service work based on different setting levels, so that the setting levels have a hierarchy according to which the settings are inherited from top to bottom. The initial settings are already made during commissioning, i.e. they are customized for your own work community and only need to be changed when necessary.
The hierarchy and inheritance of settings are described below.
Settings in Working community level
The most common rules in the working community for all users. Most of the settings are set on the working community level, as it makes it easier to manage and edit the settings. You can find these settings in Worktime > Administration > Working community settings.
Settings in setting group level
Settings group settings can be used to make exceptions to working community settings. The setting groups are often made, for example, according to the different TES’ used, in which case each setting group has settings according to the TES. The settings made in a setting group apply to all its members, unless they have different settings on a lower level (user settings). Settings are inherited from the upper setting group level to the lower setting group, unless otherwise specified on a lower level. The setting group hierarchy is displayed in the setting group list with the lower setting groups indented below the upper. In the example image below you can see upper setting group level "7.5h monthly paid, from hour to hour to balance" and below it setting group "part-time 60%".
In the example picture, the settings flow from the upper setting group to the Part-time 60% group, unless different settings have been defined in this setting group. The setting group "8h monthly paid Mon-Sun" is on the same level as "7.5h monthly paid, hourly to balance" and the rest of the setting groups in the list, so the settings are not inherited from each other. The upper level of all these setting groups is Working Community level. The settings group settings can be found in Worktime > Administration > Settings groups > Function: Settings group settings.
Settings for persons
Settings for a specific user only, such as a lower accrual of annual leave at the beginning of the employment or a temporarily agreed shorter work obligation. It is not recommended to make too many settings behind individual users as it is easier to manage settings from one location (setting group / working community level). User settings can be found in Worktime > Administration > Persons > Function: Person settings.
Inheriting settings according to the hierarchy described above works in practice so that when the service checks the settings, it first looks for a setting on the user level. If no setting is defined for the user level, the service switches to the setting group level. If there is no setting on the setting group level, the setting used comes from the working community level.
Inheritance can be prevented by saving an empty value in the name of that value. This same logic applies to all settings, meaning that inheritance can be prevented in all settings. The exception is integration rules (External Services), where inheritance is prevented by saving an empty value in all three fields: Description, Salary code, and Integration rule.
If inheritance is prevented, the setting uses the default value in the service. The default value depends on which field is in question. The default value can be a numeric value (for example, the default working day length is 0 hours, unless otherwise specified), or it can mean that the setting is not valid at all. Several default values comply with the Working Time Act.
For example, if you want to prevent the inheritance of a supplement from a higher setting group to a lower setting group, proceed as follows (the same method applies to all fields, for example work increments):
1.Select the setting group to which you do not want the setting to be inherited. Go to Setting group settings > Work hours - Supplements.
2.Select the index (number) of the supplement that you want to prevent from inheriting settings. For example, if supplement 'Mileage allowance' is saved in index 1 in a higher setting group, select supplement #1.
3. Open the validity tool for the Name field. Save an empty field as the value. Choose the validity times for the change.
4. Save the changes.