Skip to content

Data Isolation

Every customer’s data is scoped to that customer in the application’s data-access code, not just hidden in the interface.

  • Records belong to your account’s organization (your supplier record).
  • The application filters reads and writes by that scope in the query itself.
  • Regression tests check that a request from one customer’s account cannot read or modify another customer’s records on the routes they cover.
  • A page that fails to render data for you shows your own empty state, never another company’s data.
  • Isolation depends on the application applying the supplier scope on every route. Database row-level security is turned on, but today it only blocks the database provider’s public API roles; it does not separate one customer from another inside the application.
  • GovConHouse staff with administrator access can view customer data to provide support, and that access is logged.