Trust
Built to be believed.
ProofServ holds the record of your service: your company's, your workers', your properties' and your residents'. Here's how it keeps each one in its place, and how it keeps the record honest.
Who sees what
Everyone sees their part. Nobody sees more.
Access follows the relationship, not just the login. A property manager isn't a member of your company, and a resident isn't a property manager, so neither is treated like one.
| Who | Signs in with | Sees | Never sees |
|---|---|---|---|
| Worker | Email and password, in the worker app | Their own nights, with each property's notes, attention items and callbacks | The office |
| Supervisor | Email and password | The company's nights, schedule, shifts and service records, and its setup, read-only | Changing setup, people or sharing: admins only |
| Admin | Email and password | Everything for their own company, including setup, people and sharing | Any other company's records |
| Property user | A one-time code sent by email | Only the properties shared with them: nights, outcomes by location, return visits, and the observations you share | Worker names, office notes, unshared observations, other properties |
| Resident | A one-time code sent by email | Tonight's service at their own home, the property's set-out guidance, and their own requests | Worker names, photos, other homes |
How it's kept that way
Protections built in, not bolted on.
-
Each company kept separate
Every company's records are separated in the database itself, so one company's data can't be read through another company's account.
-
Checked on every request
Property and resident access is checked on the server each time a page is opened, not remembered from sign-in. Turn sharing off and it takes effect on the next page.
-
Credentials stay with their owner
Invitations and password resets go straight to the person's own inbox. Admins never see anyone's password or sign-in link.
-
Protected against bots
Sign-in, sign-up, sign-in codes and password resets are protected against automated abuse, and invitations are rate-limited.
-
Access changes on the record
Invitations, shares and changes to a resident's access each record who made them.
-
Leaving is handled cleanly
Deactivate someone and they can't sign in to the office or start new work, while their history stays. Residents who move out lose access to that home.
An honest record
The record never claims more than it shows.
A service record is only worth something if both sides can rely on it. These rules hold everywhere in ProofServ.
Evidence is described for what it is.
A photo shows what was in frame at a moment. A location fix shows a phone was nearby. Neither is presented as proof of more.
"Accounted for" means a recorded outcome.
Every location owed reached a truthful outcome on the record: collected, or an exception with its reason. It isn't a claim that software watched the work.
Shortcuts and corrections are visible.
A sweep is labelled a sweep. A corrected shift keeps the phone's original time beside the correction.
Gaps stay gaps.
A night with no visit on record says so. A request with no response says so. Nothing is filled in after the fact.
Have questions from your team?
Book a call and we'll walk your operations, IT or legal team through exactly how ProofServ handles access and records.