How is access to PeopleMuster protected?
Access to PeopleMuster is protected in layers. Sign-in needs a one-time code sent to the work email. Roles built from sixty-four permissions decide what each person reaches. Access rules are enforced in the database, not only on the screen. Sensitive records stay masked until opened, and every change lands in an audit trail.
Sign-in is only the front door. What matters just as much is what an account can reach once inside, and what trace it leaves.
Layer one is the code. No password exists to steal, and Turnstile bot protection sits in front of the form.
Layer two is the role. Each role carries a chosen set of the sixty-four permissions, so a person reaches the modules their job needs and nothing more.
Layer three sits under the screens. Access rules are enforced in the database as well, not only in the interface.
Layer four is masking. Staff feedback arrives with names hidden until a reviewer reveals one. The performance event log is admin-only and hidden behind a reveal. Meeting risk signals are admin-only as well.
Layer five is the record. Every create, update and delete goes into the activity log with the old value and the new one, the person and the time. An unexpected edit is easy to find.
Around all of it, the app is served over HTTPS only, with strict browser security headers.
Related questions
Who can change permissions?
An administrator, from the roles screen. Every permission change is written to the activity log with its old and new value.
Is staff feedback masked from managers?
Feedback arrives with identities masked by default. A reviewer has to choose to reveal a name, item by item.
What does every employee keep, whatever their role?
A fixed baseline: marking their own attendance, requesting leave, logging their own recent hours, editing their profile basics and seeing the directory.