How to check that each customer only sees and changes their own information
If your app stores customer names, orders, notes, files, or payment status, you need to prove that one customer cannot open or change another customer’s information. Here is a simple way to test it from the outside.
before you start
Use two test customer accounts and compare what each person can open, edit, search, print, and download.
What this means in simple words
in plain words
Your app should treat each customer like they have their own locked drawer, even if all customers use the same app.
If your app stores customer information such as names, addresses, bookings, notes, support messages, files, or order history, one basic rule must always stay true: a customer should only be able to see and change their own information. For a beginner, the easiest way to understand this is to imagine two customers standing next to each other. Each person should only be able to open their own drawer. If one person can open the other drawer, even by accident, the app has a serious problem.
Developers call this tenant isolation, and the technical name for the ownership check is authorization. You do not need to be an expert to test it. Create two test customer accounts. Put different sample information in each account, such as different names, notes, and orders. Then sign in as the first customer and look around. After that, sign in as the second customer and repeat the same steps. If anything from account A appears while using account B, or if account B can change anything owned by account A, the separation is broken.
- ▸Use two different customer accounts with clearly different sample information.
- ▸Compare what each account can view, search, edit, print, and download.
- ▸Treat any mixed names, files, notes, or orders as a failure.
common risk
Account A signs in and can open an order page that actually belongs to account B because the app checked that the person was signed in, but did not check who owned the order.
what to do now
Create two customer test accounts now and fill them with different sample records so you can easily spot mixed information.
ask your AI
I need you to review my app so each customer can only see and change records they own. Add ownership checks everywhere customer information is shown or changed, including lists, single record pages, edit forms, searches, printed pages, and downloads. If a record does not belong to the signed-in customer, show nothing from that record and block the change.
Why this matters for real customers
in plain words
If one customer can see or change another customer’s information, trust breaks fast and the mistake can spread through many screens.
This matters because customer information is not just text on a screen. It can include home addresses, order totals, appointment times, uploaded files, messages, payment status, and internal notes. If the app mixes these up, one customer may read another person’s information, download the wrong file, or change a booking they do not own. Even if the mistake happens only on one screen, the customer will see it as a broken promise: they trusted your app with their information, and the app showed it to the wrong person.
A common beginner mistake is thinking the app is safe because the main home screen looks correct. In reality, information can appear in many places. Developers call these data paths. The information might stay hidden on the main screen but still show up in search results, printed pages, receipt files, or old saved links. That is why you need to test more than the obvious path. You are not only checking whether people can sign in. You are checking whether the app confirms ownership every single time it shows or changes customer information.
- ▸Customer information can leak through search, print views, files, and saved links.
- ▸A correct home screen does not prove the rest of the app is safe.
- ▸Ownership must be checked every time information is shown or changed.
common risk
The customer dashboard looks fine, but a search for an order number returns another customer’s receipt and address.
what to do now
Write down every place in your app where customer information appears, not just the main screen, and test each one with both accounts.
ask your AI
List every place in my app where customer information can appear or be changed. Include list screens, detail screens, search results, forms, printed pages, receipts, exported files, and any other customer-facing output. For each place, enforce a check that the signed-in customer owns the record before showing or changing it.
A common risk beginners miss
in plain words
The danger is often not the screen you first test. It is the direct link, the download, the print page, or the saved record number.
A very common problem appears when the app protects one screen but forgets another. For example, the list of orders may only show the signed-in customer’s orders, but a direct page for a single order may still open someone else’s record if the app trusts the record number in the page address. Another frequent problem is a file download that is created from the wrong record. The screen may look correct, but the downloaded receipt or PDF may contain another customer’s information. These mistakes happen because the app checks one step and skips the next one.
Developers call one version of this object-level authorization. In plain words, it means the app must verify the owner of each individual record, not just whether the person has entered the app. To test this safely, use account A and try to open a saved link, printed page, or downloadable file that belongs to account B. You are not trying to break in. You are confirming that the app refuses to cross the customer boundary. The correct result is a clear stop, an empty result, or a return to the right customer area, with no other customer information shown.
- ▸Test direct links to a single record from the other account.
- ▸Test edit forms, printed pages, and all download buttons separately.
- ▸Expect a block, blank result, or safe return, never the other customer’s information.
common risk
Account A changes one number in the page address and reaches account B’s note page, then the app lets the note be edited.
what to do now
Try opening and changing one record from the wrong account on purpose, and confirm the app blocks both viewing and editing.
ask your AI
Make record ownership checks happen on every single-record page and every record update. Do not rely on the page address, saved links, or record numbers alone. Before showing, printing, downloading, or changing a record, verify that the signed-in customer owns that exact record. If ownership does not match, return no record data and block the action.
What to do now
in plain words
Run the same simple two-account test across screens, files, and edits, then repeat it whenever the app changes.
Start with a small repeatable test. Create two customer accounts with clearly different sample names, orders, and notes. Sign in as account A and note what you can see, search, print, and download. Then sign in as account B and repeat exactly the same steps. After that, use account A to try opening one direct link or record from account B and try one edit that should be refused. Also check generated files such as receipts, reports, invoices, or exported tables. Read them carefully, because files often contain more information than the screen shows.
Keep this test for the future. An app that is safe today can become unsafe after a new report, a new search box, or an AI-made rewrite of a customer screen. VibeCodeWall checks the public app from the outside and watches for important changes over time, which helps you keep noticing when customer boundaries may need another review. Still, your own habit matters most: repeat the two-account test after every important app change that touches customer information, printed output, downloads, or editing rules.
- ▸Keep one repeatable two-account test plan for every important app change.
- ▸Inspect downloaded files line by line, not just screens.
- ▸Repeat the checks after new searches, reports, forms, or AI-generated rewrites.
common risk
Months later, a new report page is added and suddenly every customer can see all orders because the new page skipped the ownership check.
what to do now
Save a permanent test routine with two customer accounts and rerun it after every important change involving customer information.
ask your AI
Create a permanent safety checklist inside this project for customer ownership checks. Use two test customer accounts with different sample records. For every important change, automatically review all customer information views, searches, edit actions, printed pages, and downloads to confirm each customer only sees and changes their own records. If a new feature is added, require the same ownership check before it is considered complete.
Quick checklist
- 01Create two normal test accounts for two different customers.
- 02Sign in as each account and open the same screens.
- 03Confirm account A never sees account B’s names, orders, notes, files, or payment details.
- 04Try editing a record from account A that belongs to account B and confirm the app blocks it.
- 05Check list screens, item details, edit forms, search results, printed pages, and downloads.
- 06Make sure blocked attempts show no other customer information.
- 07Check exported files, receipts, and PDFs for mixed customer information.
- 08Repeat the same checks after every important app change.
- 09Ask your AI builder to enforce ownership checks every time information is shown or changed.
FAQ
What is the fastest beginner test for this?
Use two customer test accounts with different sample information. Compare every screen, search, file, print view, and edit action. If one account can ever see or change the other account’s information, the app needs a fix.
Do I need to test downloads and printed files too?
Yes. Files often contain extra rows, notes, addresses, or totals that are not obvious on the screen. A page can look correct while a receipt, PDF, or export still includes another customer’s information.
What should the app do when someone tries to open another customer’s record?
It should refuse the request without showing the other customer’s information. A clear stop message, an empty result, or a safe return to the person’s own area are all acceptable outcomes.
Can this problem come back after I fix it once?
Yes. A new search, report, edit form, or AI-generated change can reopen the problem. That is why you should repeat the same two-account test after every important update and keep watching the public app over time.