Project Config
The Project Config component copies the global configuration settings of your Supabase project.
What Is Copied
Authentication Providers
OAuth provider configuration:
- Google — Client ID, Client Secret, redirect URL
- GitHub — Client ID, Client Secret
- Apple, Discord, Azure, etc.
- Email settings (SMTP, templates)
- Phone settings (Twilio, etc.)
PostgREST Settings
- Schemas exposed via the REST API
- Default role
- Maximum row size
Auth Settings
- Session duration
- Email confirmation enabled/disabled
- MFA enabled/disabled
- Allowed redirect URLs
Why Clone It?
If you are creating a staging environment or migrating a project, configuration settings must be identical for your application to work the same way:
- Users can sign in with the same providers
- The REST API exposes the same schemas
- Session rules are the same
Key Considerations
| Situation | Behavior |
|---|---|
| OAuth secrets (Client Secret) | Copied — the target uses the same credentials |
| OAuth callback URLs | Copied as-is — remember to update them for the target environment |
| SMTP settings | Copied — staging will send emails from the same SMTP server |
Warning for staging: If you clone the project config to a staging environment, the OAuth and SMTP settings point to the same services as production. Consider:
- Updating the OAuth callback URLs for the staging domain
- Disabling or changing SMTP to avoid sending real emails from staging
Next Steps
- Auth Users — User accounts
- Component overview — All components