Access Modes and Environments

Floo has an app-level access mode that controls who can open your app.

Access Modes

The public CLI configuration surface currently exposes:

[app]
name = "my-app"
access_mode = "password"

Shipped backend validation currently enforces:

If you request a gated mode on an unsupported plan, the deploy/app update fails with a plan feature error.

When a password-mode app is deployed, Floo can generate or store a shared password for that app. Use:

floo apps password my-app

The dashboard app settings page also exposes the password for password-protected apps.

floo_accounts is the access mode for named user access. In the shipped dashboard:

Those user-management flows are dashboard-first today. The CLI currently covers org membership, not per-app end-user access grants.

The current CLI deploy path reads access mode in this order:

Example:

[app]
name = "my-app"
access_mode = "password"

[environments.dev]
access_mode = "public"

Mode	Best for	Main surface
`public`	marketing sites, open APIs, internal previews	config + deploy
`password`	private demos, client previews, temporary staging	config + `floo apps password`
`floo_accounts`	apps with named end users and allowlisted signup	config + dashboard Users flows