Signed-in access only
Every protected page needs an authenticated session. Anyone who is not signed in is sent back to the login page.
Security and data
HR software holds some of the most personal information a business keeps. This page sets out what PeopleHalo does today to control who sees it and to keep a record of changes.
In place today
Every protected page needs an authenticated session. Anyone who is not signed in is sent back to the login page.
Employees, HR and management, and the Super Admin each see only their own navigation and pages. Employees see their own records, not their colleagues'.
ID documents, CVs, agreements and other HR files are tied to authorised users. They are not stored as public files on the website.
When attendance or break records are corrected, the audit log keeps who made the change, the old and new values, the reason, the source, the IP address and the time. Only the Super Admin can read it.
The Windows Desktop Agent, now in pilot, signs in with the employee's own account. The server checks the account and its access token before it accepts any action, and the agent only acts during an active shift.
The server, not the browser, enforces the important rules: one attendance record per shift day, and no deleting a shift that people are still assigned to.
Still to be published
Answers to these will be published on this page. Until then, ask us directly at contact@peoplehalo.com.
Questions about data?
PeopleHalo is developed and operated by Stream Labs Design. We are happy to walk your team through how access and records work.