Skip to main content

Clock-In Settings — configure company clock-in rules

Use this guide to update Clock-In Settings (general rules, thresholds, notices) for your organisation.

Sarah Murray avatar
Written by Sarah Murray
Updated over a week ago

Before you start

  • Access is permissions-based. If you can’t see Clock-In Settings, ask a Company Admin.

Open Clock-In Settings

  1. Click the cog icon (top-right).

  2. Select Clock-In Settings from the dropdown.

Configure settings

General

  • Allow Clock-In Without Shift?
    Tick the checkbox to let employees clock in even if they aren’t assigned to a shift.

Thresholds

  • Clock-in/out leeway
    Set grace periods for late/early clock-ins and clock-outs.

  • Auto-approval
    Toggle on to automatically approve on-time clock-ins.

  • Automatic clock-out type

  • Time: choose a fixed Automatic clock-out time from the dropdown.

  • Duration: enter a Duration (hours) or use the arrows to set how long after clock-in the system should auto clock-out.

Notices

  • Company notices
    Add messages shown during clock-in and clock-out (two text boxes).

  • Visible company events
    Choose which events appear to employees at clock-in/out.

Save changes

  • Click Save (green button).

Tips

  • Use Auto-approval for standard shifts to cut admin.

  • Prefer Duration for varied shift patterns; use Time for fixed-end-time shift patterns.

  • Keep Notices short and action-oriented (e.g., “Wear name badge; complete end-of-day checklist”).

Troubleshooting

  • Save is greyed out: Ensure any required fields are set (e.g., select a time when using Time auto clock-out).

  • Automatic clock-out not triggering: Confirm the type (Time vs Duration) matches your use case and values are valid.

  • Employees can’t clock in without a shift: Check Allow Clock-In Without Shift? is enabled under General.

  • Can’t see Clock-In Settings: You may lack permissions—ask your Company Admin.

  • Need help? Click the chat button in the bottom-right corner of the screen to contact our support team.

Did this answer your question?