Bolt app shows a database permissions error on a new table (tables private by default since Oct 30, 2026)
Short answer: Bolt changed a default. Starting October 30, 2026, Bolt database keeps new tables private, and your app needs explicit permission to read or write them. Tables in existing databases aren't affected. So if a feature you added recently, built on a new table, shows a database permissions error, or just shows nothing, the new table probably has no permissions yet. Bolt says you can ask it to fix the table permissions. Ask for only what each kind of user needs, and don't make private tables public.
The fix: ask Bolt to set permissions for that table
Bolt's release notes say that when Bolt creates a new database it should set up the right permissions for you, and that if you see a database permissions error, you can ask Bolt to fix the table permissions. Be specific, so the fix is safe as well as working. Paste this into the Bolt chat:
Since October 30, 2026, new Bolt database tables are private by default, and my app gets a database permissions error (or shows no data) on a feature that uses a newer table. Please:
1. List every table my app reads or writes, and say which ones were created after October 30, 2026.
2. For each of those, add permissions for only what the app needs: logged-in users can read and change only their own rows; logged-out visitors get read access only if a page really must show that data to them (for example a public list).
3. Do NOT make every table public and do NOT remove the protection from tables that hold private data.
4. Tell me exactly what permissions you added for each table before you apply them.
5. Make the app show a clear error message instead of an empty page when a database request is refused.
6. From now on, whenever you create a new table, set its permissions in the same change.
When it's done, publish again so your live site gets the change, then test it (see "Check that it worked" below).
Signs this is your problem
- You (or Bolt) added a feature with a new table after October 30, 2026, and that feature fails while older pages still work.
- You see a database permissions error in your Bolt project, or in your browser's developer tools (Console or Network tab) when you use that feature.
- The page just looks empty, or saving does nothing. Many AI-built apps hide database errors, so a refused request can look like "no data yet".
How to confirm it
- Note when the failing table was created. If it was created on or after October 30, 2026, this change applies to it. Tables in databases that already existed are not affected, according to Bolt.
- Open the failing page in your live app, then open your browser's developer tools (right-click, Inspect) and look at the Console and Network tabs while you repeat the action. A refused database request with a permissions message points to this change.
- Try a page that only uses older tables. If that works and the new feature doesn't, the new table's permissions are the likely gap.
- Try the feature both logged in and logged out. If it fails only for one of them, that kind of visitor is the one missing permission.
Why it happens
A database table can be open to anyone who uses your app, or private until someone grants access. Bolt's release notes say Bolt database now keeps tables private by default, so your app needs explicit permissions to read or write information. That's safer: a new table isn't exposed before anyone decides who should see it. But if the permissions are never added, the app is refused too, and the feature looks broken.
Bolt says this applies to new database tables created after October 30, 2026, and that existing databases aren't affected.
What not to do
- Don't make every table public to make the error go away. That stops the error but lets anyone read what's stored there.
- Don't give logged-out visitors write access unless a page really needs it, and then only to that one table.
- Don't keep re-prompting "fix the error" without saying how private the data is. Say who should see which rows.
Check that it worked
- In a private window, log in as a normal test user (not an admin) and use the feature. Rows you create should show up, and you should see only your own.
- Log in as a second test user. They should not see the first user's private rows.
- Log out and open the same page. Logged-out visitors should see nothing private.
Using Supabase with Bolt instead of Bolt database? Supabase made a similar change for new tables: see My new Supabase table says "permission denied for table". Settings that differ between preview and the live site are a separate cause: see My app works in preview but breaks in production.
Common questions
Why does my Bolt app show a database permissions error on a new table?
Bolt's release notes say that starting October 30, 2026, Bolt database keeps tables private by default, and your app needs explicit permissions to read or write them. This applies to tables created after October 30. If a feature that uses a newer table shows a permissions error, this change is a likely cause.
Are my older Bolt database tables affected?
Bolt says the change applies to new database tables created after October 30, 2026, so existing databases aren't affected. If an older page also broke, look for a different cause.
How do I fix a Bolt database permissions error?
Bolt says you can ask Bolt to fix the table permissions. Ask it to add permissions only for the tables and actions your app really needs, so logged-in users read and change only their own rows, and not to make every table public to fix the error.
Should I just make the table public to fix it?
Not for private data. Making a table readable by everyone stops the error, but then anyone can see what's stored there. Grant only what each kind of visitor needs, and keep each user's rows private to them.
How AppFirstAid helps
Our free check reads your live site from the outside, like a visitor, with no signup. It can't see your database permissions settings, and it never logs in or reads your data. If your site's public code talks to a Supabase project, the report adds a heads-up about new tables needing access, with the tables your code uses, and for an app whose owner has proved it's theirs, it asks (counting only, never reading rows) whether those tables answer a logged-out visitor. A journey test, on an app you've proved is yours, signs up, logs in and tries checkout like a real first-time customer, with a screenshot of each step, so if a new table breaks sign-up, login or checkout you see the exact step that failed. See pricing for what each costs.
Source, read November 11, 2026: Bolt support release notes, week of Oct 26 – Nov 1, "Bolt database tables are now private by default" (the October 30 start date, tables private by default with explicit permissions needed to read or write, applies only to new tables created after October 30 so existing databases aren't affected, Bolt should set permissions when it creates a new database, and you can ask Bolt to fix table permissions). Bolt may change these details. AppFirstAid is not affiliated with Bolt.
Check your live app in under a minute
AppFirstAid's free check looks at your live site from the outside: leaked keys, files left in public, safety settings, and whether your sign-up, login and checkout pages open. No signup. Journey tests go further: a simulated first-time user (a real browser) signs up, opens your email, logs in and tries checkout, and shows you the step that broke. Your first journey test is free.
Run the free checkSettings move around as these tools update. If a menu name has changed, look for the same words nearby. Spotted something out of date? Tell us.
More guides
- Stripe says they paid, but nothing unlocked in my vibe-coded app
- Login broke after I added my custom domain (Supabase redirect URLs)
- What built-in security scans miss in AI-built apps
- Supabase confirmation emails not arriving for new users
- Supabase "permission denied for table" (error 42501) on a new table: why it happens and the fix
- My app works in preview but breaks in production (environment variables differ)
- Stripe webhook fails with 401 on a Supabase Edge Function
- Error 400: redirect_uri_mismatch on Google sign-in (or "The JavaScript origin in the request does not match")
- Lovable app launch checklist: how to test your Lovable app before launch (sign-up, email, login, checkout)