Row-level security
Row-level security is a database feature that decides, row by row, which records a given account may read or change, so that the database itself, not only the application on top of it, keeps one customer’s data away from another’s.
Why it matters in shared software
In software used by many hotels at once, a table holds rows belonging to all of them. Without row-level security, the separation lives in each query the application writes, and one forgotten filter shows one hotel’s guests to another. With it, the database applies the rule to every query by itself, and a query that forgets the filter still returns nothing it should not.
What to ask a supplier
Is the separation enforced by the database or only by application code? Which tables does it cover? Who on the supplier’s side can work across customers, and is what they change recorded?
Where Wizorks shows it
Wizorks keeps every hotel’s records apart with row-level security enforced by the database itself, so hotels never see one another’s data. Wizorks’ own operations staff and scheduled jobs work across hotels, and the changes our staff make are recorded in our own activity log.