Handle backend credentials deliberately
Know where connections are configured and avoid exposing privileged credentials in browser flows.
Backend connections and browser-delivered actions serve different purposes. Review how a credential will be used before adding it to a project.
Configure the intended connection
Open Backend and choose the service you need. Supabase uses an API URL and a credential field to obtain its schema. Firebase's mobile-notification setup asks for a project ID and a service-account JSON file.
Use only the credential appropriate to that integration and the access it requires. A successful connection test does not prove that the key is suitable for every published browser request.
Keep browser actions limited
An HTTP action's URL, headers, and client-side behavior should be designed for browser use. Do not place privileged server credentials in a browser-delivered flow. Use an appropriately authenticated backend endpoint when an operation needs private server-side authority.
Review access when the project changes
Check backend permissions independently of component visibility and app-side conditions. Showing a user name or hiding an edit button does not by itself restrict record access.
If a credential is no longer needed or may have been exposed, rotate or revoke it with the service that issued it and update the connection that depends on it. Test the affected flows again after changing credentials.