Configuration and credentials
Put each setting in the part of the system that uses it.
Three places settings belong
| Setting | Owner |
|---|---|
| Project startup and dependencies | The project’s files and approved runtime configuration. |
| Coding and speech credentials | The host/provider configuration. |
| Application service secrets | Your application backend or its secret store. |
Use the settings exposed by the installed build. Developer source setups can have different configuration paths from packaged desktop apps.
Configure only what you use
You do not need an account with every supported service. Configure the provider or integration you intend to use and omit unused optional entries. An empty key does not enable an integration.
For Supabase-backed applications, public project configuration and privileged management credentials serve different purposes. A management token or service-role key must never be shipped in browser or phone code.
Apply and verify a change
- Record which component uses the setting.
- Update it in that component’s supported configuration.
- Reload or restart only the component that needs it, saving work first.
- Test one operation that actually uses the integration.
A populated configuration field proves only that a value was saved. Check authentication, permissions, and a real request before treating the integration as ready.