Skip to main content
Use this guide when you are deciding who can operate Floo and who can open an app you deployed on Floo.

Prerequisites

  • you are authenticated with floo auth login
  • you know whether you are changing org membership or app access
  • for password and floo_accounts, your plan is Pro or above

1. Manage your Floo team

Organization membership controls who can operate apps and billing for your org.
floo orgs members list
floo orgs members set-role <user-id> admin
floo orgs members set-role <user-id> member
floo orgs members set-role <user-id> viewer
The shipped dashboard Team page also supports invites and pending invite management.

2. Choose an app access mode

Configure app access in floo.service.toml or floo.app.toml:
[app]
name = "my-app"
access_mode = "password"
Available public modes in the current CLI docs:
  • public
  • password
  • floo_accounts

3. Work with password-protected apps

If an app uses password mode, retrieve the shared password with:
floo apps password my-app
The app settings view in the dashboard also shows that password and lets you copy it.

4. Manage named app users

If an app uses floo_accounts, the shipped dashboard exposes two app-level controls:
  • a domain allowlist for self-registration
  • individual user grants and revocations
Those flows live in the app’s Users tab today. The CLI currently does not expose matching per-app grant or domain allowlist commands.

5. See users across the org

The shipped org-level Users page shows people who have logged into your floo_accounts apps, plus:
  • which apps they have used
  • first seen / last active timestamps
  • basic user search

What To Use Where

TaskCLIDashboard
change org member rolesyesyes
invite teammatesnot first-classyes
retrieve shared app passwordyesyes
manage app user grantsnoyes
manage allowlisted domains for signupnoyes
inspect org app usersnoyes

What To Do Next