Platform security
Protect sessions and security features
Founderled needs a private boot secret before it can protect sessions, provider tokens and two-factor setup.
Do this in your cloud deploymentReady
Session-backed features, provider-token protection and two-factor authentication can use the configured secret.
Next steps
- 01Create a long random value in your hosting provider's secret manager.
- 02Add it to the Founderled deployment as SESSION_SECRET and redeploy.
- 03Return here and re-check the status before connecting real credentials.
What proves it is done
Founderled reports only whether the secret is present. It never renders the value.
Founderled cannot safely rewrite its own boot secrets from a public page. The cloud or provider owns that action; this page tells you exactly what to configure and gives you the re-check when you return.