Shift Change Requests
Shift change requests are controlled by a single company-level setting, Allow employee shift change requests, in Settings → Attendance Settings. When it is enabled, employees are able to raise a request to change the shift they are assigned to instead of the change being made only by an administrator. When it is disabled, shift assignments are managed exclusively from the Shift Roster.
Who can use it
- Company Admin / users with HR administration permissions — turn the setting on or off in Attendance Settings, and manage shift assignments in Shift Roster.
- Employees — can raise shift change requests only while the setting is enabled.
Prerequisites
- The shift the employee should move to must already exist. Shifts are managed in Shift Roster; a custom shift can be added alongside the default General Shift (9:00 AM–6:00 PM, Monday–Friday).
- The employee must already have a shift assigned in the Shift Roster.
How to Access
Attendance Settings: Sidebar → Settings → Attendance Settings → toggle Allow employee shift change requests.
Shift Roster: Sidebar → HR → Shift Roster (/account/shifts) — where shifts are created and employees are assigned to them.
Attendance records: Sidebar → HR → Attendance (/account/attendances).
Steps
1. Enable the setting
Open Settings → Attendance Settings and enable Allow employee shift change requests. This is a per-company setting and applies to all employees in the company. Other options on the same screen — such as Allow clock-in outside shift hours, employee self clock-in/clock-out, and the attendance reminder toggle — are independent and unaffected.
2. Create the target shift, if needed
If the shift an employee should move to does not exist yet, add it in Shift Roster before the change can be applied. Custom shifts can be created beyond the default General Shift.
3. Apply the shift assignment
Once a change is agreed, the employee's shift assignment is updated in Shift Roster. Recurring shift assignments send one notification per series, and they honor the notification toggle on the assignment — so employees are not notified repeatedly for a single recurring series.
4. Confirm the new shift is in effect
Check the employee's record in Attendance (/account/attendances) after the change to confirm clock-ins are being evaluated against the new shift.
Effect on other features
- Clock In / Clock Out — the assigned shift determines clock-in behaviour. A late mark is applied 20 minutes after shift start, and clock-in outside shift hours is permitted only when the Allow clock-in outside shift hours setting is enabled. The sidebar clock-in widget is shift-aware.
- Maximum check-ins per day — 2 by default, and configurable per shift. When more than one check-in per day is allowed, the extra check-in is stored as additional fields on the same day's attendance record rather than as a separate row.
- Shift Rotation — rotations are configured under Shift Rotation (available from both the HR module and Attendance Settings) and are executed with Run Rotation. A rotation reassigns shifts according to its own rules, so it can override an individually applied shift change.
- Notifications — Shift Assign is one of the configurable notification event types, and shift notifications can also be delivered to Slack via the per-event checkboxes on Settings → Notification Settings → Slack (one-way, PMSuite → Slack).
- Attendance Report — available at
/account/attendance-report.
Limitations
- Attendance deletion is permanent. Records removed from the Attendance module (
/account/attendances) are hard-deleted with no recovery path — there is no trash or soft-delete. Workaround: export a copy of attendance data before making any deletions, and verify each record before removing it. - The setting is company-wide, not per department or per employee. There is no per-group control over who may raise a request. Workaround: keep the setting disabled and handle shift moves centrally through Shift Roster, where an administrator applies each assignment.
- Shift Rotation can supersede an individual change. If the employee belongs to a rotation, the next Run Rotation applies the rotation's shifts. Workaround: review rotation membership in Shift Rotation before applying an individual change, and remove the employee from the rotation if their new shift must persist.
- Clock-in IP checks are unreliable on dynamic IPs. If Clock-in check with IP address is on, employees moving to a new shift may be blocked or wrongly allowed. Workaround: use this check only with a static IP address; otherwise rely on the location-radius check instead.
Troubleshooting
- Employees can't raise a shift change request — confirm Allow employee shift change requests is enabled in Settings → Attendance Settings. It is a company-level setting, so a change applies to everyone.
- The desired shift isn't available — the shift must be created in Shift Roster first.
- The employee is being marked late after the change — late marks are applied 20 minutes after shift start. Verify the employee is now assigned to the intended shift in Shift Roster and that the shift's start time is what you expect.
- Employee reports a missing second clock-in — additional check-ins are stored on the same day's attendance record, not as a separate row. Open that day's full record rather than looking for a second entry in the list.
- Duplicate assignment notifications — recurring shift assignments send one notification per series and respect the notification toggle; if notifications are unwanted, turn the toggle off when creating the assignment.