Test Record Access in an AI-Built Base44 Web App

A generated page may hide an action in the interface while leaving access to the underlying record too broad. Verify the entity's data permissions with ordinary accounts before adding real users.

Worked example

Two-account ownership acceptance fixture

User Alex creates B-DEMO-01.
User Riley creates B-DEMO-02.
Alex sees and edits B-DEMO-01 only.
Riley sees and edits B-DEMO-02 only.
Signed-out visitor sees neither booking.

Steps

  1. Create a practice Base44 app with a Booking entity and two non-admin test users. Add one synthetic booking per user using the app so record ownership follows the same path as it will in use.
  2. In the app's data permissions, configure owner-based access for the operations the feature supports. Review read, create, update, and delete separately and use the app's reporting or admin role only where it is needed.
  3. Sign in as each test user and check that each can see and update their own booking. Confirm the account does not receive the other user's private record in the app.

What to check

  • Repeat the tests in the published staging app using regular user sessions. An admin preview can see data that an ordinary user should not receive.
  • If a feature reads data through a service-role backend function, check that function's user and record permissions as well. Service role access bypasses entity-level rules.

See the Base44 tool profile

References