Staff and team management on Vareons: a complete HR system for Egyptian stores

Staff management on Vareons lives at /dashboard/staff and brings eight tabs under one roof: overview, employees, attendance, leaves, payroll, performance, reports, and access control. That split is deliberate: the first six tabs are HR (the employee's record, attendance, leave, salary and review), and the access-control tab governs entry to the dashboard itself.

The internal design rests on two subsystems that serve two different jobs over the same collection. The access-control side stores the employee against the merchant id (merchantId) with email, password, role and status, and is what enables login and permission enforcement. The HR side stores the extended employment record — joining date, date of birth, national id, address, contract type, contract end date, probation end date, emergency contact — plus basic salary and bank details. Vareons shows both in one place and merges the login account with the HR record by matching id, and it can create a new HR record for the employee when you save the create or edit form.

Adding a team member starts at /dashboard/staff/create: first and last name, email, password, role, department and employee id, then the employment section, then salary, then the permission matrix. The password is stored hashed and never in plain text. Login credentials can be emailed to the employee automatically on creation (on by default), with a separate endpoint to resend them later from the staff table. After the account exists, the team member signs in with their own account scoped to your store and sees only what you allowed.

The heart of team management is permissions. Every staff member has a per-section matrix: each dashboard resource — customers, orders, products, inventory, discounts, staff, settings and the rest — has four independent toggles: view, create, edit and delete. Those toggles are stored as separate permission rows per staff member and resource. On top of that, the staff account itself carries a role and a status (active, inactive, suspended), its password is locked for thirty minutes after five failed login attempts, and the session is issued as a token carrying the staff user type, the merchant id and the permissions with a seven-day life. This is why a staff member from another store cannot reach your data: every query is scoped to the merchant id taken from their own session.

The employees tab lists the team in one view with their record, employment details, salary and status, with soft add, edit and delete plus a list export. The overview tab gives a quick picture: total and active staff, present today, absent today, on leave, attendance rate, this month's payroll total, and the number of leave requests still waiting for your approval. Alongside it are important alerts: birthdays in the next thirty days and contracts expiring within thirty days. All of these numbers are computed from the same staff, attendance, leave and payroll records, so nothing is entered twice.

Attendance is the first column of daily operations. Each staff member has one attendance record per day that cannot duplicate (one date per employee per day), carrying check-in and check-out times and the day's status: present, absent, late, half-day or leave. The system computes actual work hours from the difference between check-in and check-out, and automatically computes overtime beyond eight hours. You can record attendance directly from the dashboard for one employee or the whole team, and the numbers roll up into today's attendance rate and monthly reports, and feed later payroll deductions for absence and lateness.

Leaves have a clear request-and-approval path. An employee requests leave by type: annual, sick, emergency, unpaid, maternity, paternity or other, and the number of days is computed automatically from the start and end dates. Requests appear as pending until a manager approves or rejects them, and who approved and when is recorded. Vareons keeps default balances per type — 21 days annual, 15 sick, 5 emergency, 90 maternity and 3 paternity — and deducts approved leaves from them, so used and remaining are always visible.

Payroll gives attendance and leave their practical meaning. Vareons generates the month's payroll for all active staff; each record has a basic salary, allowances (housing, transportation, food, other), bonuses (performance, project, holiday, other) and overtime in hours and rate, then deductions (tax, insurance, absence, lateness penalty, loan, other), and gross and net are calculated automatically. Each record has a payment status — pending, processing, paid or failed — with a button to mark it paid, a full export of payroll to a CSV file that handles Arabic, and amounts shown in Egyptian pounds.

Performance reviews combine numbers and behaviour. Each employee is reviewed over a monthly, quarterly, semi-annual or annual period, combining weighted KPIs at 60% of the score with six competencies — technical, communication, teamwork, leadership, problem solving and initiative — at 40%. The final score is out of one hundred and yields a rating: excellent, very good, good, fair or poor. A review also records strengths, areas for improvement, upcoming goals and training recommendations, and can be saved as a draft, completed, or acknowledged by the employee.

Reports come in six kinds: attendance, payroll, leave, performance, headcount and turnover. Beside them, quick insights compare the current period with the previous one across four measures: average attendance, total payroll, leave utilisation and average performance. Reports open in a print-ready window, so they can be saved as a PDF in one action and are suitable for sharing team numbers with partners or accountants.

What makes staff management on Vareons fit Egypt is that it is not a separate module bolted onto the store but a layer over the same tenant data: the employee belongs to your store, their permissions decide what opens in your dashboard, and attendance and payroll run in Egyptian pounds with Arabic and English dates and a bidirectional interface. More importantly, the team itself can work on the store safely: an orders employee sees orders, an inventory employee sees inventory, without every role seeing everything. On top of this, the dashboard's AI copilot has twelve read tools over staff and HR data (overview, a full employee profile, access list, employees, attendance, leaves, performance, payroll and insights), so you can ask the assistant about your own team and get an answer from your own data under the staff view permission. That is how staff management on Vareons joins account and permission administration with day-to-day HR in one place, whether the team is large or small.