uttek HR

Roles decide: HR sees all files; bank, tax and social security data as well as salaries only with the dedicated “sensitive data” permission. Line managers see their team without sensitive data and decide requests; only decision-makers see the reason for a sick note. Staff only see themselves and non-confidential documents in “My area”.

The software runs on your server. Sensitive fields and salaries are stored encrypted and masked in the file; showing them is logged. Every access to a file, document or export is in the access log. After leaving, per document type and for sick notes, retention periods delete the data automatically; data access as a file and erasure on request are built in.

Staff choose the type and period on the phone; working days, half days and bank holidays are counted automatically and the remaining leave is checked. The line manager gets the request, sees overlaps in the team and approves or rejects – in Enterprise optionally with a second step in HR. Remaining leave carries over at year end and expires on the configured date.

No. uttek HR is the HR administration before it: files, contracts, holidays, deadlines. In Enterprise it creates a monthly list with hours, holidays, sick days and changes for your payroll office or payroll software as PDF and CSV.

Yes, from Pro via uttek Connect: staff, qualifications and approved absences go to uttek Rota, Time and Dispo – without salary, bank details or the reason for sickness. Closed months from uttek Time appear as the hours balance in the file, jobs from uttek Dispo are checked against holidays and expired qualifications.

Web space with PHP 8.2 or newer. The database (SQLite) is built in; MySQL/MariaDB is optional from Pro. A daily cron job is needed for reminders, holiday carry-over and deletion periods.

Yes, without sign-up. Every visit gets its own demo database with sample data (trades business, medical practice, agency & office), deleted after 24 hours. All people and data are fictitious.

Passwords are only stored as a secure hash; new passwords need at least 12 characters and are checked offline against a list of leaked passwords. Everyone can set up two-factor sign-in via an authenticator app (e.g. Google Authenticator, Aegis) with backup codes, and the admin can require it per role. After 5 failed attempts a login lockout with increasing delay applies; “forgot password” sends a single-use link valid for 1 hour. Optionally emergency contacts, notes on staff, contracts and absences – sensitive personnel data and salaries get a second layer are stored encrypted with AES-256-GCM, with the key outside the web root. The “Security (status)” page shows all measures at a glance.