Automations
- Discover Automations
- What are automations?
- How do I access automations?
- What automations can I set up?
- What configurations can I automate in Clock ins/outs?
- What's the difference between Global and Segmented automations?
- How do I configure global and segmented automations?
- How do I personalize automation settings for an individual employee?
- How can I enable the "Clock in/out" button in the app for all employees?
- What is automatic clock out and how can I set it up?
- Can I set up an automatic clock out if employees forget to clock out?
- Can I automate a clock out in a split shift?
- What is the difference between "schedule" and "working day" in the automation "When the assigned schedule is completed the system will clock out"?
- Can I choose how time is counted in clock ins/outs with incidents?
- What is workday rounding up?
- Can I set up rounding for employee clock ins/outs automatically?
- What does "block the ability to clock in" mean?
- What does "restrict clock ins/outs by IP" mean?
- Which notifications can I automate?
- How does configuring grace period minutes affect the calculation of tardiness?
- What are validations and how can I set them up?
- What can I automate in User accesses?
- What can I automate in Section visibility?
- How do I enable my employees to request a clock in/out even if the "Clock ins/outs" section is hidden?
- What are approval flows and how do I create them?
- Can I automatically delete an access code when an employee is deactivated?
- New behavior of “Minutes of advance notice before the start of the workday”
- Can I configure automations that work as conditional triggers?
- Can I configure how many minutes before clock-in time an employee's clock in will be blocked?
New behavior of “Minutes of advance notice before the start of the workday”
We’ve implemented an important change in how the Minutes of advance notice before the start of the workday automation works.
From now on, this automation works the same way as the rest of Sesame’s automations. This means that if there is a configuration set in the employee’s profile and a different one in the company’s general settings, the employee profile configuration will be applied.
This is an important point to keep in mind, as the configuration hierarchy has changed.
Previously, the company’s general configuration always took precedence for this notification, regardless of what was defined in the employee’s profile. From now on, this is no longer the case: the individual employee configuration takes priority over the general company configuration.
We recommend keeping this in mind to avoid unexpected behavior when sending notifications.
The general configuration for this automation can be found at the following path:
Configuration >> Automations >> Notifications >> Send a notification prior to the start of the employee's schedule/shift.
If you need to define this notification differently for one or more employees, you must do so from each employee’s profile:
Employees >> [Employee name] >> Automations (side menu) >> Send a notification prior to the start of the employee's schedule/shift.
That’s it! You can set a general configuration for the entire company, and whenever you need to configure the notification differently for one or more employees, you can do so from their individual profiles. This way, each employee’s specific configuration will apply only to them and will take precedence over the company’s general settings.