Default settings related to leave policies


Changing the display name of Leaves feature

Read following -

https://amoeboids.atlassian.net/wiki/spaces/UD/pages/2468347945/Company+name+Features+Project+restrictions#Company-name-%26-features

Leaves statuses

Apart from the https://amoeboids.atlassian.net/wiki/spaces/UD/pages/3001155609 , there are two configurable leave statuses in the system. As UpRaise admin, you can decide whether you want following statuses to be associated or not.

  • Availed - past dated - To identify the leaves that were added for the past dates. 

  • Availed - without approval - To identify the leaves that availed without explicit approval. 

These two statuses will help you identify the leaves that were added for the past dates & the ones that were availed without explicit approval.

If these statuses are required, just enable these statuses as shown in the above image.

Leaves visibility

As shown in the below image, there are two options to set leave visibility. You can use these options together or can also go with one of them.

Optional leave visibility

If this option is turned on, then it you can what will be the default visibility option so whenever someone is requesting a leave, visibility option is selected by default. Of course they can override the selection but this way you can avoid a situation where people have mistakenly shared their leave requests with all users/wrong users/teams.

If this option is turned off then there will be no visibility setting on the leave request pop up

Enforced leave visibility

If this switch is turned on, you can enforce the visibility of leaves to selected users/teams those will always be in the visibility list of leave request and these users/teams cannot be modified by users while applying for a leave.

If this setting is turned off then the leaves will be visible based on optional visibility settings as mentioned above.

Some cases of using this setting are -

  • In some organizations, it is mandatory to share all leaves with one or more teams. For example - HR team, executive teams, etc. 

  • In some organizations, it is mandatory to share all leaves with one or more users. CEO, Head of the departments, etc.