Stormguard Timesheets

Manage logins

Latest 20 account access changes

My Admin recovery email

Keep your username/PIN login. Verify an email you control as a separate recovery route. Enter it here privately.

Overtime approval

Approve a time window for a named person. All times below are UK time. Normal shifts finish separately; start an overtime shift when the approved window begins.

Test permissions — Admin only

Allow a named user to test outside working hours. Maximum four hours; test records are excluded from management totals. All dates and times below are UK time.

Start a shift

Normal hours: Mon–Thu 08:00–16:30; Fri 08:00–13:30 (UK).

Your approved windows

My day

Start a production job

Your jobs

Record additional completed units. Full quantity finishes a job automatically; starting another job pauses the previous one.

Saved production entries

H&S declaration — before production

Specification sign-off

Your login records who signed. Sign once per SO/WO in your shift; use the comment box if another operator checked the work.

Downtime stopwatch

00:00:00

Your shift downtime

Record waste

You can add waste during production or after a job finishes.

Your shift waste

My shift summary

Downtime breakdown

Total accounted time combines the production estimate, measured downtime and specification stopwatch time. Overlapping downtime and specification intervals are counted once. Production is estimated from completed units × (CNC seconds + loading allowance); this is not the full elapsed shift length. Untimed specification checks have no measured duration.

Atlas program & clamp-bed setup

Your login and the time are recorded with the setup. For a shared job, a changed setup pauses recording until the crew acknowledge it. Sign the check again whenever programs, clamp-bed setup or the job changes.

S.O / W.O History

Saved orders, machine allocations, checks and recorded production. Managers and Admins only.

New good units are the units added by that production entry. Allocations and checks do not add output. Shared Atlas output appears once per saved increase; expand Operator credits to see each share. With an operator filter, matching machine output and that operator's credited output are shown separately. TEST entries are labelled; they remain excluded from management KPIs. Older records may lack an SO or machine reference; missing details are shown as “Not recorded”. This history follows event dates, which can differ from KPI shift-start dates.

Logged in — Admin only

Active means the website checked in within the last 90 seconds. Not responding means a session remains open but the website has stopped checking in, for example after a browser closes or loses connection. It is not a confirmed logout.

Reason for signing users out or pausing access

Sign-out blocks that website session's server access. An open page returns to sign-in on its next check or request. Saved work stays on the server and shifts keep their normal finish schedule. A user can sign in again unless access is paused or their account is disabled. Your own account is excluded from forced sign-out; use the normal Sign out button when finished. Last recorded sign-out shows only sign-outs recorded by this update.

Recent Admin access actions

Live production Dashboard

Every machine and its current operators · available to all signed-in users

Production view

This board shows saved entries and recorded activities, with a fresh snapshot every 15 seconds while visible. Production time is an estimate: completed units × (CNC seconds + loading allowance). Remaining job time is also an estimate. Shift countdowns use the server's approved finish time and keep ticking between refreshes. Today's totals follow UK shift-start dates, including completed shifts; each operator's credited units and production estimate cover their current shift. A shared Atlas job counter is the whole job total and can span shifts. Atlas operating choices are grouped as one physical machine. Operators remain on shift until they leave/end it or its scheduled finish is reached, even if their browser is signed out. Login/session controls stay private to Admin.

Security · Admin only

Loading security status…

Server protection checks

The server checks these protections once a minute. When armed, a failed check locks website access. If checks stop for over three minutes, website data access closes pending review. This does not inspect internet traffic, detect every hack or prove the system is secure.

Security controls

Reason for this action

Keep automatic locking off until installation and recovery testing are complete. Disarm before approved server changes; the Supabase console must review and accept the new baseline before you re-arm.

Emergency: close website access

This locks out every user, including all Admins and recovery logins. Saved work remains. Shifts keep their normal finish schedule. Reopening requires the Supabase project's SQL console after investigation.

Type LOCK SYSTEM to confirm

Recent security events

Blocked unapproved identities are warnings. Incorrect PINs and ordinary unknown visits do not shut down the system. Authentication attack monitoring and traffic protection require separate controls.

Management KPI DATA

Detailed reports and supervisor alerts for Managers and Admins.

Sign in

Admin recovery