Connect application data with Supabase

Describe the data you need

Tell the assistant what the application should store, who can read it and who can change it. Distinguish an example dataset from real records. A visually complete form is not a connected database until its actions and access rules have been implemented and tested.

Supabase is a native project integration. Connect the intended account when the project requests it, and review the selected organization and database project. The native provisioning flow can prepare the database before continuing repository and hosting setup.

Check a small data flow

1. Confirm which Supabase project is linked to the application.
2. Ask for the required tables, fields and access rules using the application’s actual requirements.
3. Create an appropriate test record and check that it persists after reloading.
4. Test both allowed and denied access with the relevant user roles.
5. Review database changes before using production data.

Resolve provider restrictions

A provider project limit, an overdue provider bill and an expired authorization are different problems. Read the connection or provisioning status and address its reported cause. Retry only when the cause has been resolved.

A version restoration changes application code; it does not undo stored data or migrations. Keep backups and migration review separate from the application’s version history.

Next steps

• Connect a service
• Restore an earlier code version
• Choose a hosting provider