Skip to main content
This page covers the people and programs that operate floo: your org’s members, their roles, and the floo API keys they use. Who can open your app is separate; see App sign-in.

Manage your floo team

floo orgs invite <email> --role <admin|member|viewer> defaults to member; the role applies when the invite is accepted. The dashboard Team page also sends invites and manages pending ones. Every org member uses one builder seat, whatever their role: An invite past the limit fails with PLAN_LIMIT_MEMBERS. App users, the people who sign in to an accounts app, do not use seats.

What each role can do

A member’s org role caps every key they hold. Demoting a member also lowers what their existing keys can do.

floo API keys

floo auth login signs in through the browser and stores a key in ~/.floo/config.json. For CI, scripts, or an agent without a browser, create a key from Settings → API keys in the dashboard, or with POST /v1/auth/api-keys and a scope of read, write, or admin. Without a scope, the key gets your current effective scope. You cannot create a key above your own role; that fails with SCOPE_ESCALATION.
A key acts only in the org it was created in. The raw key is shown once; store it in your CI secret store. A call above the key’s scope fails with INSUFFICIENT_KEY_SCOPE. Give each automation the lowest scope that works: read for dashboards and monitors, write for deploy and release pipelines, admin only for billing or member management. App API keys, which let programs call your app, are different; see App API keys.

Require SSO for floo sign-in

Enterprise orgs can require SAML or OIDC sign-in for floo members with floo orgs sso. On other plans it fails with ENTERPRISE_SSO_REQUIRED. This controls sign-in to floo itself, not to your app.

Provision members with SCIM

Enterprise orgs can add and remove floo members from their identity provider with SCIM, so a person who leaves your company loses floo access when they are removed there. Email sales@getfloo.com to connect your directory.

Audit log

Org admins see the audit log on the dashboard Audit page and can export it as CSV. Every plan gets the same log: who changed what in your org and its apps, including deploys, env var changes and reads, database queries, API keys, and member changes. Events are kept for 90 days. Reading the log or its export needs an admin floo API key.

Next steps

App sign-in

Choose who can open your app and manage app users.

Billing and spend caps

Set spend caps and manage billing.