password and accounts require Pay as you go or above.
1. Manage your floo team
Organization membership controls who can operate apps and billing for your org.2. Choose an app access mode
access_mode is a config-as-code knob in floo.app.toml. The next git push applies it to your app. No dashboard click is required.
public: open access (default)password: shared password (Pay as you go+)accounts: per-user auth via gateway-managed sign-in (Pay as you go+)
access_mode value. Contact sales if you need it.
Where the value lives
[app] access_mode is the default for every environment. [environments.<env>] access_mode overrides it for dev, prod, or preview:
accounts or password to public; an authenticated floo redeploy can. Setting password needs a shared password to exist first; create it in the app’s access settings. Placing access_mode anywhere else, such as inside [services.web], does nothing.
3. Work with password-protected apps
If an app usespassword mode, retrieve the shared password with:
4. Manage named app users
If an app usesaccounts, the CLI supports explicit invitations and memberships:
[auth] in floo.app.toml; the next deploy applies it to the target environment:
invite admits only people you invited, domain lets anyone whose email matches a domain in the existing allowlist register, and open lets anyone sign up. The allowlist cannot be extended because its dashboard/API management controls were retired; it is not a config key. Push, release, and promote cannot loosen access_policy; an authenticated floo redeploy can.
The dashboard also exposes individual user grants and revocations. The CLI does not expose the email-domain list.
5. See users across the org
The shipped org-level Users page shows people who have logged into youraccounts apps, plus:
- which apps they have used
- first seen / last active timestamps
- basic user search
What to use where
What to do next
Access modes
Review the access-mode model and plan gating.
Budget controls
Set spend caps and manage billing.