Quick answer
Every record in ASHR.work is tagged with your organisation. The database itself enforces that a query can only ever return rows carrying your tag — a safety rule called row-level security. So even by accident, one company's data can never leak to another. Your data stays private and separate.
How is my data kept separate?
Every single record — each employee, leave request and document — carries a tag saying which organisation it belongs to. When ASHR.work looks anything up, it only ever fetches rows that carry your tag.
Record Organisation tag
Leave request Acme Ltd
Payslip Acme Ltd
Document Acme Ltd
A request from Acme Ltd can only return rows tagged Acme Ltd. Anything tagged to another company is simply invisible.
What is row-level security?
Row-level security is a rule built into the database. It checks the organisation tag on every row before it is returned. Rows that do not match are never handed back, no matter what asks for them.
Why enforce it in the database, not just on screen?
Screens can have bugs. If separation lived only in the app, a mistake could show the wrong data. By enforcing it deep in the database, the protection holds even if something in the app goes wrong. It is a second, stronger lock.
Can another company ever see my data by accident?
No. Because the database refuses to return another company's rows, an accidental leak between organisations cannot happen. Your data stays yours.
Frequently asked questions
- Is separation enforced only on screen?
- No. It is enforced deep in the database, so even a mistake in the app cannot leak another company's data.
- What tags a record to my company?
- Every record carries your organisation's ID, and the database only returns rows that match yours.