Employee master
The central employee master: maintain all staff with their core data, employment and contact details in one place – independent of the app login.
Live preview — real view with sample data
M30 · Employee master
| Last name | First name | Department | Position | Employment type | Start | Status |
|---|---|---|---|---|---|---|
| Kraus Logistik | Bauer & Co. | Entry 2 | Entry 5 | Reviewed | 10/06/2026 | ✓ |
| Bauer & Co. | Wolf Spedition | Record 3 | Record 6 | Open | 21/06/2026 | — |
| Wolf Spedition | Roth Handel | Item 4 | Item 7 | In progress | 02/07/2026 | ✓ |
| Roth Handel | Meyer GmbH | Entry 5 | Entry 8 | Done | 13/07/2026 | — |
| Meyer GmbH | Kraus Logistik | Record 6 | Record 9 | Reviewed | 24/07/2026 | ✓ |
Not a screenshot: the same interface you get in production.
What you do here
Create employees and maintain person data (first name, last name, employee number), employment (department, position, start and end date) and contact details (email, phone, mobile). This master is the HR anchor and is not tied to login accounts – it describes the person, not the access.
Status & history
Use „Deactivate“ to hide employees who have left without deleting them; the „Former“ tab brings them back and „Activate“ restores them. Start and end date as well as creation and update timestamps document the history.
Who sees what
Admin and dispatcher can create, edit, delete and toggle employees active or inactive. Drivers only have read access to the directory and cannot change anything themselves.
Tips
Use the search across name, employee number and email to find someone quickly, and the „Full-time“ and „Part-time“ tabs to filter by employment type. Capture employment type and start date right when creating a record – that keeps reports and handovers to payroll and dispatch clean. Use „Set employment type“ to change it quickly without opening the whole form.
What's inside
- Employees
- Employee
- Edit employee
- Add employee
- Edit
- Delete
- Set employment type
- Deactivate
Fits together with
Other blocks from the same area.
Absence
Here staff request holiday and report absences (sickness, home office, special leave); the back office approves or rejects them – with an optional stand-in.
M29Client master
The central client master for care: maintain all clients with their core data, contact, address and care level in one place – the foundation for routes, visits and documentation.
M31Member master
The central member master: maintain all club members with their core data, membership, fee and contact details in one place – independent of the app login.
M32Shift planning
Plan shifts per staff member here – as a calendar or list.