{"slug":"supabase","title":"Supabase","summary":"Save the project URL and an account access token. The assistant then creates tables, row-level security, Edge Functions, and function secrets.","body":"In Connections, open **Backend** and choose Supabase.\n\n## What to paste\n\n1. In the Supabase dashboard, open the project, choose **Connect**, and copy the project URL. It looks like `https://abcdefghijklmnopqrst.supabase.co`.\n2. Create an access token from your Supabase account (click your avatar, open **Account preferences**, then **Access Tokens**), not from the project's API settings. It starts with `sbp_`.\n3. Paste both and save.\n\nA classic token covers everything. A scoped token needs read-write on Database, Edge Functions, and Edge Function Secrets. The token is shown only once, so copy it before you leave the page.\n\nThat token is all the assistant needs. It reads the project's API keys itself.\n\n> [!NOTE]\n> If you do not want to use an account token, paste the anon key and the service role key from **Project Settings**, then **API Keys**. The assistant can then use the data API but cannot run SQL or deploy functions for you.\n\n## What to ask for next\n\nTell the assistant the backend is connected and what the data must represent. It writes the SQL, the row-level security policies, and the Edge Functions, and pushes named secrets from the vault. You do not create the schema by hand.\n\n```\nSupabase is connected. Add email sign-in. Store each member's bookings in a\ntable with the class, the time, and the member. Members can only read and\ncancel their own bookings.\n```\n\n## Keys a function needs\n\nWhen an Edge Function calls another service, such as an email provider, add that key under [API keys and secrets](/docs/secrets). The assistant sets it as a function secret by name.","sectionSlug":"connect","sectionTitle":"Connect services","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"connections","title":"Connections"},"next":{"slug":"firebase","title":"Firebase"}}