Base44 list empty or 403 for normal users (but fine for admin)? Fix the permission rule
Your Base44 app works perfectly when you test it. Then a real user signs in and the list is empty, a record they should see says Record not found, or saving throws a 403 Forbidden. As the owner, everything looks fine. T
Your Base44 app works perfectly when you test it. Then a real user signs in and the list is empty, a record they should see says Record not found, or saving throws a 403 Forbidden. As the owner, everything looks fine.
This is one of the most common things I see when I check Base44 apps: it isn't missing data and it isn't a Base44 bug. Base44 hides records that a permission rule denies, so a denied read looks like an empty list, and a denied create or update throws a 403. Here's how I find which rule is blocking people and fix it.
What you might be seeing
-
403 ForbiddenorPermission deniedwhen a user saves something - A list that is empty for users but not for the admin
-
Record not foundwhen a user opens a record you know exists
Why it happens
- You tested as the owner. As the app owner or an admin you pass rules that ordinary users fail, so the problem only shows up once real users sign in.
- No rule matches the user. Read is limited to Creator Only, but the records were created by an admin or an import, so no ordinary user is the creator.
- The visitor isn't signed in. A condition that compares to the user needs a signed-in caller. Anonymous visitors are blocked outright, not treated as "false".
- The field name doesn't match. An Entity-User Field Comparison names a field that doesn't exist on the table, or is spelled differently, so it never matches anyone.
Find the cause first
Before changing any rule, spend five minutes reproducing it:
- In preview, use Test Permissions and act as the affected user.
- Note exactly what fails. An empty list or "not found" is a denied read. A 403 when saving is a denied create or update.
- Open that table's Permissions page and read the rule for that action.
- Check who created the records. Imported records, or records an admin created, will never match Creator Only for an ordinary user.
That last point catches a lot of people. If you seeded a table from a CSV and then locked Read to Creator Only, none of those rows were created by your users, so they see nothing.
Fix 1: Add the rule your users actually need
Pick the rule that matches who should see each table:
- Shared reference data (categories, products, settings): set Read to All Users. Remember that in Base44 All Users means anyone, so only do this for data that is meant to be public.
- Records assigned to people (tasks, tickets, bookings): use an Entity-User Field Comparison on the assignment field, typed exactly as the column name.
- Records each user creates (their own orders, notes, submissions): keep Creator Only, and make sure users create those records themselves rather than an admin creating them on their behalf.
If admins also need to see everything, add a User Property Check on User Role equal to Admin alongside the user rule. A person who matches any one rule gets access, so the two rules work together.
Fix 2: Require sign-in where rules compare to the user
If a page reads user-specific data, a signed-out visitor will always be blocked by a rule that compares to the user, and they'll just see an empty page. In your app's access settings, require login for those pages, so visitors are asked to sign in instead of seeing nothing.
Check the fix worked
Don't stop at "the admin view looks right". Test it from the other side:
- Act as an ordinary user: the list shows the records they should see.
- Save a record as that user: no 403.
- Act as a different user: they still can't see the first user's private records.
The third check matters. The quickest way to make an empty list go away is to open the table to everyone, and that trades one problem for a much worse one.
Stop it coming back
- Test every table as an ordinary user before publishing, not only as the owner.
- Write down who should see each table in one sentence. It makes the right rule obvious, and it makes a wrong rule easy to spot later.
Questions people ask
Is the empty list a Base44 bug? No. Hiding denied records is deliberate, so the app doesn't reveal what exists. It just looks like missing data.
Can I give admins access to everything? Yes. Add a User Property Check on User Role equal to Admin next to the user rule; a person matching any rule gets access.
What if fixing this keeps opening data to everyone? Then the permission model needs a design, not another patch: decide who owns each record and who may see it, then write and test the rules for each role.
Sources: Base44 developer docs: Entity security and Base44: Managing data permissions.
The full checklist, with related Base44 fixes, is on our fix page. If you'd like a second pair of eyes, our free AI-built app audit lists what's broken in your code, with the file and line.
I wrote this with AI assistance and reviewed it myself.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.