Settings & Admin

Global Settings

What the agency console Settings page controls: how clocked time becomes paid time, the pay week, premiums, the Sage file layout, and optional AI features.

Talk to us Browse all guides

Overview

Setup > Settings, agency console.

The Settings page holds system-wide rules. Changes apply to every client straight away. Settings that belong to one client (approval, PIN policy, notifications) are on the client; settings that belong to one site (geofence, kiosk speed, camera feed, site rules) are on the location.

Payroll Policies

How clocked time becomes paid time.

Setting Choices
Walk-in clock-ins (no booking) Do not pay: flag as a walk-in and require a booking afterwards (recommended); or pay actual hours.
Cancelled, sick or AWOL shifts Do not pay (an admin can grant with a per-shift adjustment; recommended); or pay actual hours.
Multiple shifts on the same day Which booking a clock matches: closest start (recommended), earliest, or longest.
Pay week starts on The first day of the pay week, used by weekly overtime, Close week and the weekly exports.
Approval cut-off When the week's hours should be approved after the week ends. Used by the Pilot KPIs late-approval measure.
When premiums overlap Stack them (multiply the uplifts) or pay only the single highest premium.
Premiums on shifts over midnight Use the day the shift started, or split at midnight so each hour gets its own day's premium.
Automatic lunch deduction Deduct at least the lunch length, or only when no break was logged. Each rate rule sets the length and trigger.
Shifts with no charge rate Charge £0.00 with a warning (recommended), charge at the pay rate, or £0.00 without a warning.
Site weekly overtime threshold Whether a site's overtime rule is used for pay when the rate rule has no threshold of its own.

Sage Payroll Export

The layout of the Sage file.

Choose the Sage product, the employee reference, name format, date format, where department and cost centre come from, and the payment reference for each pay element. See The Sage Payroll File.

Face Recognition

Use the Face recognition page.

The match threshold that the kiosk applies is set per client on Setup > Face recognition, together with the anti-photo check, PIN policy and face match proof. See Facial Recognition Explained.

Important

The Minimum Match Confidence slider on this page is an older setting and does not change kiosk matching. Use the per-client threshold on the Face recognition page instead.

Kiosk Settings

Mostly per site now.

Kiosk speed settings (express mode, result screen time) are per site, on Sites > Kiosk setup.
The browser kiosk unlock PIN is set for your system and shown to administrators on the Kiosk setup page. The Admin PIN field on this page does not change it. The Android kiosk app uses its own exit PIN, set on each tablet.
Camera Stream Interval sets how often a kiosk sends a camera frame when a site's camera feed is switched on (it is off by default).
Overtime Alert Threshold is used by the AI anomaly hints. Overtime pay comes from rate rules, and the Exceptions page uses the site's rules (48 hours a week where none is set).

Ada (AI Features)

Optional and off by default.

AI features (dashboard brief, assistant chat, timesheet anomaly hints and report summaries) need an Anthropic API key and are each switched on here. They are off unless you switch them on, and they never receive face data, photos or PINs. Anthropic is listed as a sub-processor (United States) in our privacy policy.

Know who turned up, and pay every hour right.

Face-verified clock-ins, live geofencing and payroll-ready timesheets in one system. Tell us how your shifts run and we will show you how it fits.

App hosted in the UK · Onboarding led by a pilot site · No app needed to clock in