orgs

Manage organization members, invitations, Enterprise SSO, and the active org.

members list

List all members of the current organization.

floo orgs members list

Members:
  User ID                               Email                Role
  a1b2c3d4-...                          alice@example.com    admin
  e5f6g7h8-...                          bob@example.com      member
  i9j0k1l2-...                          carol@example.com    viewer

JSON output

{
  "success": true,
  "data": {
    "members": [
      {
        "user_id": "a1b2c3d4-...",
        "email": "alice@example.com",
        "role": "admin"
      },
      {
        "user_id": "e5f6g7h8-...",
        "email": "bob@example.com",
        "role": "member"
      }
    ]
  }
}

members set-role

Change a member’s role.

floo orgs members set-role a1b2c3d4 member

Arguments

Argument	Description
`USER_ID`	User ID of the member
`ROLE`	New role: `admin`, `member`, or `viewer`

Examples

# Promote to admin
floo orgs members set-role a1b2c3d4 admin

# Downgrade to viewer
floo orgs members set-role a1b2c3d4 viewer

# Agent workflow: set role and confirm
floo orgs members set-role a1b2c3d4 member --json 2>/dev/null | jq -r '.data.role'

JSON output

{
  "success": true,
  "data": {
    "user_id": "a1b2c3d4-...",
    "role": "member"
  }
}

invite

Invite a user to the current org with a role, in one step. floo sends an invite email and returns a one-time invite link; the role is assigned on acceptance, with no separate members set-role call.

floo orgs invite teammate@example.com --role admin

✓ Invited teammate@example.com to acme as admin.
  Invite link: https://app.getfloo.com/invites/<token>/accept
  An invite email was also sent.

Arguments

Argument	Description
`EMAIL`	Email address to invite

Flags

Flag	Description	Default
`--role ROLE`	Role granted on acceptance: `admin`, `member`, or `viewer`	`member`

JSON output

{
  "success": true,
  "data": {
    "email": "teammate@example.com",
    "role": "admin",
    "status": "pending",
    "invite_url": "[REDACTED]",
    "expires_at": "2026-03-08T14:00:00Z"
  }
}

invite_url is a one-time link and is redacted in --json output unless you pass the global --reveal-secrets flag. status is pending until the invite is accepted or revoked.

switch

Switch the default org for subsequent commands. Useful when you belong to more than one org, the chosen org is used to resolve --app and org-scoped commands until you switch again.

floo orgs switch acme

Arguments

Argument	Description
`ORG_SLUG`	Org slug or ID to make active

sso

Inspect and manage Enterprise SSO for an organization. These commands require an Enterprise plan; on any other plan they fail with ENTERPRISE_SSO_REQUIRED.

floo orgs sso status
floo orgs sso doctor --org acme
floo orgs sso portal --no-browser
floo orgs sso enforce
floo orgs sso enforcement disable

Command	What it does
`status`	Show the live SSO connection and enforcement state
`doctor`	Diagnose provider reachability and current credential compatibility
`portal`	Open a short-lived provider setup portal
`enforce`	Verify with SSO in the dashboard and enable enforcement
`enforcement disable`	Verify with SSO in the dashboard and make SSO optional

Every sso command takes --org ORG (slug or ID; defaults to the current org). portal, enforce, and enforcement disable take --no-browser to print the URL instead of opening it.

Errors

Code	Meaning
`NOT_AUTHENTICATED`	Run `floo auth login` first
`INVALID_ROLE`	Role must be `admin`, `member`, or `viewer`
`ENTERPRISE_SSO_REQUIRED`	`floo orgs sso` needs an Enterprise organization plan

CLI

Config

members list

JSON output

members set-role

Arguments

Examples

JSON output

invite

Arguments

Flags

JSON output

switch

Arguments

sso

Errors

​members list

​JSON output

​members set-role

​Arguments

​Examples

​JSON output

​invite

​Arguments

​Flags

​JSON output

​switch

​Arguments

​sso

​Errors

members list

JSON output

members set-role

Arguments

Examples

JSON output

invite

Arguments

Flags

JSON output

switch

Arguments

sso

Errors