Connect Supabase for backups (read-only role)

Backups need a database user that can read everything and change nothing. Vigavo calls it vigavo_ro.

One-click (when available)

Step 3 of the project wizard offers Connect with Supabase. You approve access in Supabase, pick the project, and Vigavo creates the read-only role once. The access token is used for a few calls and then thrown away; it is never stored. If the button says "coming soon", use the manual way.

Manual

1. In step 3 (or the Backups tab) open Advanced. Vigavo shows SQL with a freshly generated password.
2. Run it in the Supabase SQL editor. It creates vigavo_ro, grants read access to the public, auth and storage schemas and sets BYPASSRLS, so backups include every row regardless of your RLS policies (the role still cannot write).
3. Copy the pooler connection string from Supabase (Project settings, Database), replace the user with vigavo_ro and the password with the one from the SQL, and paste it into Vigavo.
4. Vigavo tests the connection before saving it. Problems: Connection test failed.

The connection string is stored encrypted with your account's key and never shown again. Storage file backups (on plans that include them) need a Storage key on the Backups tab.