Connect a Bolt app

Create a login for the walker

Open your published app and sign up with a fresh email you control. Give FixWalk that email and password on the connections screen. The walker uses this account and no other.

Link your repo

Bolt can push your project to GitHub from the project menu. Pick that repository on FixWalk's connections screen. FixWalk only reads it.

Give the walker a read-only database key

Read-only, always. We store it encrypted, use it only during a walk, and delete it the moment you disconnect. The walker writes only under its own account, never yours.

Bolt apps connect to Supabase through Bolt's Supabase integration, so the database steps are the same as for Lovable. In the Supabase dashboard for your project, run this in SQL Editor → New query (choose your own long password):

create role fixwalk_reader login password 'CHOOSE-A-LONG-PASSWORD' noinherit;
grant usage on schema public to fixwalk_reader;
grant select on all tables in schema public to fixwalk_reader;
alter default privileges in schema public grant select on tables to fixwalk_reader;
grant authenticated to fixwalk_reader;

Then Project Settings → Database → Connection string → Session pooler. Copy the URI, replace the user postgres.<project-ref> with fixwalk_reader.<project-ref> and the password with yours, and paste it on FixWalk's connections screen.

The last line lets the walker see the tables your app protects with row-level security, which return no rows at all to a plain reader. It reads them as its own signed-in account, never yours, and only inside a transaction that is rolled back. Leave it out and the walk still runs, reading those tables through your app's own screens and exports instead, and the report says which.