01
In the code
Every part of the software that touches records has to say which agency it’s for. A check that runs each time the software is built fails if one doesn’t.
Security
Passwords

What every client’s page says at its foot. The screens show Outsmart, a real customer. Its client here, Saltbush Provisions, is an example.
Record progress, a store address, an account ID, a collaborator code and a note asking for help. It can’t read or change anything in their platforms.
Private and hard to guess. You can switch it off, and the page stops working without losing the record.
Between agencies
01
Every part of the software that touches records has to say which agency it’s for. A check that runs each time the software is built fails if one doesn’t.
02
The database itself filters every row to the one agency being served, and the app refuses to start if that rule is missing.
03
A standing set of tests acts as one agency and tries to reach another’s records, at every way in.
Your team
Owner, admin, member, viewer. Only the owner can delete a request, a client or a person.
With an authenticator app, for anyone who switches it on.
Stored as one-way hashes, not as the password itself. Repeated wrong guesses are slowed down.
What’s kept
Reporting