Employee Management

The Employee List is a server-paginated directory of everyone in the organisation. Filter by station, department, sub-department, employee group, designation, employee status, a specific employee, user name or CNIC number, and the server returns just the matching page — the list stays quick whether you have forty people or four thousand. Active staff show by default; switch the status filter to see people on leave or the In-Active pool.

Each row is a record card, not a bare line: employee code, punch code, CNIC, user name and login state, station, department, designation, joining date and employment status, plus when the record was added and last modified. Export Data downloads every row matching the current filters as a CSV — code, name, email, station, department, designation, status and joining date — regardless of which page you are viewing.

New records are created through a five-step form: General Information, Additional Information, Company Information, Employee Documents and Salary Information. General covers names, father's name, mobile, email, reporting manager and role template. Additional holds the personal record — date and place of birth, marital status, CNIC with issuance and expiry dates, EOBI registration number and entry date, bank account, emergency contact, passport and visa details. Company places the person in the structure: station, department, sub-department, division, grade, employee group, cost centre, region and employment status, with joining, confirmation and contract dates.

Which fields are compulsory is your call. The form validates each step against the mandatory-field settings your organisation configures, with a sensible default set — first name, mobile number, email, reporting manager, gender, CNIC, station, department and employee status — that you can relax or extend per field. The same rules are enforced on the server, so a record can never be saved incomplete by another route.

Upload Excel accepts a .csv or .xlsx file — either the downloadable Nexa template or a full export from your previous HR system — and creates a record per row. The import maps dozens of columns, from names and CNIC to EOBI details, bank fields and contract dates, and it resolves structure as it goes: stations, departments and designations that do not exist yet are created on the fly, and reporting lines are wired up by employee code. A result dialog reports how many rows imported and lists exactly which rows were skipped and why.

Once records exist, Send Credentials provisions self-service logins in bulk: tick the employees, and the system generates a password for each, creates the login and emails it where outgoing email is configured — with a results table you can share otherwise.

Day-to-day changes are requests, not silent edits. The module includes Employee Profile Requests and Employee Info Requests (a tabbed form mirroring the profile), Employee Transfers that show old and new values side by side before anything moves, Resignation requests with reason and date, Suggestions and Delegation requests. Each request type has its own configurable workflow: auto-approved, or multi-level with up to five levels, where each level's approver is a specific employee or a role resolved relative to the requester — their reporting-line manager, a manager two, three or four layers up the reporting chain, or their department head. Station-level roles such as station head, station HR manager and station accounts manager can be chosen as options too; those are not resolved to a specific person, so a level configured that way falls back to any approver with the right permission.

When a request is approved, the change is applied to the employee record automatically — a transfer updates station, department and reporting manager; an approved info request writes the changed fields back to the profile. You can even set per-field rules, choosing which profile fields employees may edit directly and which require approval first. The Employee Approvals queue gathers pending requests of every kind in one filterable list.

There is deliberately no delete button on the directory. When someone leaves, the InActive action records an inactive type, exit type and leaving date, disables their login and moves them to the In-Active pool — the record and its history stay intact. A separate blacklist flag can be set or removed on any record.

Re-Hire reverses the journey: search the In-Active pool by CNIC number, pick the person from the filtered list, and their existing record returns to service with everything it already knew about them.

Employee Role manages access as a per-form permission matrix — every module, form and action (add, update, view, delete) is an individual toggle. Assign permissions per employee, copy one employee's role to another, or maintain named role templates; defaults such as Employee Self-Service, HR Manager and System Admin ship out of the box, and the server enforces the same keys on every API call.

Employee Settings holds the module's configuration in four tabs: approval workflows per request type, per-field info-approval rules, mandatory-field settings and suggestion categories — including whether a category accepts anonymous submissions.