Feature Ideas

When representative selection is optional, using a variable in the Out-of-Office (OoO) message can lead to incomplete or confusing messages if no representative is set (e.g., “During my absence, [blank] will represent me”). This feature would allow either: Conditional logic within the OoO message (e.g., “If representative is set, show this block; otherwise, show alternative text”), or Separate OoO message templates for cases with and without a representative, both for internal and external communication. This ensures clarity and professionalism in automated absence communication, regardless of whether a representative is assigned. This request is strongly tied to https://feedback.absentify.com/b/7mlokrm5/feature-ideas/disable-or-make-optional-the-availability-check-for-representatives

Currently, the representative selection dropdown only appears if a minimum number of representatives is defined for the absence type. This feature would ensure that the dropdown is always visible in the absence request form, regardless of configuration, but allows the user to optionally select a representative. This gives end users the flexibility to decide per request whether to assign a representative or not, without being forced to do so.

In scenarios like company-wide holidays or bridge days, entire teams may be absent by design. The current implementation prevents absence requests if the selected representative is also unavailable, which can block valid and intentional team-wide absences. This feature would allow organizations to either disable or make the availability check for representatives optional. It ensures that absence requests can still be submitted even when no available representative exists, aligning the system behavior with real-world operational needs.

Derzeit können ganze und halbe Urlaubstage nur auf der Ebene der Abwesenheitsart eingestellt werden. Wir würden das jedoch auf Ebene der einzelnen Abteilungen benötigen....

This feature would allow managers to assign a representative who can take over approval responsibilities during their absence (e.g., vacation). It ensures that absence requests from team members are not delayed due to unavailable approvers. The representative should be able to approve or reject requests within the same workflow, with clear visibility and auditability. This is especially useful in larger teams or during peak holiday seasons, where uninterrupted approval processes are critical. As a potential future enhancement, an API-accessible variable for the "approval representative" could be introduced, allowing organizations to automate the delegation process and integrate it seamlessly into their internal systems.

It should be possible to cancel individual days of vacation (instead of just the whole vacation). This should also be possible for managers and admins for past holidays. One implementation idea would be to be able to choose between the entire vacation and individual days when canceling vacation, and then select these specifically.

I would like to see an option to change your absence markings without cancelling them. I.e. when you try to change (shift) your vacation, you have to cancel the whole thing and start over.

Allow overtime to be added in a separate counter and then the emplyees can subtract the recup hours from this.

When a user wants to cancel an absence, the approver must also accept or refuse the cancellation

Due to events in the year, it would be useful to define dates when vacations cannot be taken. It would be useful if it can be defined which type of absences cannot be taken during the blocking dates.

Not only the approver has to approve an absence request. It is also possible to configure that a substitute must be selected for each request. It can be configured whether the requester can select a substitute from a pool, or whether he or she is free to choose one. In this process, the representative gets a request when the representative approves, only then the request goes to the approver.

At present, only representatives who are available for the entire duration of the application can be selected. However, in practice, internal arrangements often stipulate that if a representative is only partially absent, their tasks are partially taken over by a stand-in and, for the remaining period, by another person. Therefore, it would be desirable for the system to accommodate such scenarios—for example, by allowing multiple representatives to be assigned for different segments of the application's time period.

In education our attendance policy needs to escalate sickness management to formal procedures where staff meet an eight day threshold in any rolling 12 month period. Is there a way this could be flagged up or exported? A sort of managers overview that signifies when action is needed or staff are in the danger zone.

Have a function where you can add staffs weekly working hours, not just working patterns. Be able to run reports to show what a departments headcount, FTE or total hours are or a whole business.

The ability to set a 'finishing' date / cessation date would be useful to calculate leave days taken and entitled to at point of cessation!!