Administration — people, time, pay and the audit trail

Where it is: Home
Administration
Who can open it: EveryoneEveryone — but an employee sees a different screen, titled My Work, holding only their own schedule, attendance, leave, payslip, tasks and their own log entries.
Tabs: Overview
People
Attendance
Leaves
Payroll
Tasks
Activity Log
What it writes: User accounts, usernames, roles, branches, departments, schedules and pay rules
Departments
Attendance records and corrections
Leave requests and their approval
Salary advances, deductions and payslip payments — with a cash registry expense
Tasks, one record per assignee
Announcements, with their own expiry
Employee documents, in the database and in storage

My Work — the same screen, on an employee’s account

An employee’s tile is called My Work, and it holds two tabs rather than seven: Overview and Activity Log. Everything on it is about them.

The card at the top is the punch clock. It states where you stand — On duty, Checked out or Not checked in — with Today’s shift beside it, which reads either the hours, On leave or Day off. The one large button is Check in, and Check out once you are on.

Under it, your own figures and lists:

Card	Holds
Worked today · Leave remaining · Net this month	The three numbers, for you
My payslip	Base, Additions, Deductions and Net, with See what was deducted and Print payslip
My leave requests	Yours, as Pending · Approved · Rejected. Empty, it says You have no leave requests.
My tasks	Assigned to you, by deadline. Empty: No tasks assigned to you.
My documents	Your contract, ID and certificates, as filed by an administrator

The three things you can ask for are in the title row, and they are requests, not actions: Request leave, Request advance, Fix attendance — the last one for the shift you forgot to clock in or out of.

Administrators only

Overview

Team KPIs and the approval queues. The tabs carry counts when something is waiting — Leaves3 means three requests need an answer, and a tab with nothing waiting shows no number at all.

Announcements

Post it with a Title (The kitchen closes at 4 today), optional Details, Who sees it — Everyone, specific departments, or specific people — and Show it for: today only, 3 days, a week, two weeks, a month.

People

Create an account
1. Administration
2. People
3. + User
Username — They sign in with this — plus name, role, branch and, optionally, a department: a branch is where they work, a department is who they work with.
A taken username is refused: That username is already taken. Renaming one later updates every record that stores this name.
Set the schedule
The weekly pattern of working days and hours.
This moves money
The weekly pattern below drives payroll. Lateness, absence and overtime are all measured against it, so a wrong shift start is a wrong payslip.
Set pay and rules
Base salary, overtime rate, annual leave days, and Lateness rules — checked in this order; the first rule that applies wins.
Attach documentsoptionalاختياري
1. a person
2. Documents
Contract, ID / permit, certificate or other, with a label and an optional Expires on — only for documents that actually expire, like an ID.
Note
An expired document is badged, never hidden. The moment it expires is exactly when you most need to see it. Documents also outlive employment: a deactivated person’s contract stays readable, because it is evidence.
See their devicesoptionalاختياري
1. a person
2. Devices
Every browser signed in to that account, with a sign-out per row: Ending a session signs that device out as soon as it is online.

Roster, filters and the Org view

Active Deactivated All pick the roster; the Filters2 panel narrows it by department, branch, role and setup state.

The results line carries a quiet count — 12 users · 3 need setup — where “needs setup” means one of five gaps that make a record half-useful: no department, no branch, no schedule, no base salary, no email. A deactivated account has no gaps by definition.

Org switches from the roster to the structure: departments grouped by branch, company-wide first.

Changing many people at once

Select rows, then Edit….

Hard to undo

The readout is the confirmation. The dialog states, live, what each switched-on field will do, to how many people, who is skipped and why, and how many already have that value. A bulk change that would write nothing says so before the button, not after.

Rules it holds itself to:

A field you did not switch on is not written — not null, not whatever its control happens to show.
A shift change writes the weekly template and leaves individual pinned dates alone, so a team-wide change does not wipe the day one person already has off.
You cannot change your own role in a bulk edit — you would take the screen away mid-write — and any change that would leave the shop with no active administrator is refused outright.
Deactivation is a confirm, not an undo, and the message names the departments that would be left without a manager first.
Everything else finishes with an Undo in the toast, which writes the previous values back through the same path, skips anything someone else changed meanwhile, and says how many.

Announce on a selection pre-fills an announcement’s audience.

Attendance

Today’s attendance, plus the correction queue. An employee who forgot to clock in files a correction; you approve or reject it here.

Leaves

Requests with their type, dates and balance. Each person’s remaining balance — Leave remaining and Taken this year — is shown beside the request, so the decision does not need a second screen.

Payroll

Per month, per person: base, overtime, deduction breakdown, advances taken, and the payslip.

Control	Does
Pay from	Which branch and safe the money leaves
Payment method	How it is paid
Deduction (−)	A manual deduction on top of the computed ones
Payslip	The printable slip

Tasks

Assign a task with a title, an assignee and a deadline.

Activity Log

The audit trail, most recent 200 entries, live.

Role	Sees
Administrator	Everything, with filters by search, user, type and date
Employee	Only entries tied to their own orders. No filter card

Each entry carries what happened, who did it, when, and — where the action was about an order — a link straight to that order.

The log is where a bulk edit and its undo appear as two separate lines. An undo does not erase the record of the change; it records that it was undone.