First-run onboarding
The first time anyone logs into a new Flero instance, the system runs a short onboarding wizard to capture your organization name and a few defaults. If onboarding is already complete (someone else set it up, or you're joining via invite), you'll skip straight to the workflow list and can ignore this page.
You'll know you're in onboarding when the URL is under /onboarding/… and there's no left sidebar, the wizard is full-screen.
Step 1, Welcome (/onboarding)
The welcome screen introduces Flero and shows three feature cards (visual editor, integrations, deployment flexibility). It's purely informational.
📸 Screenshot needed:
onboarding__welcome.png, the Welcome screen with the three feature cards and a prominent Get started button.
Click Get started to continue.
Step 2, Organization setup (/onboarding/setup)
Create the organization, the top-level container that owns your first workspace.
📸 Screenshot needed:
onboarding__org-setup.png, the Organization setup form with name field, optional description, and the "Continue" button.
Fields:
| Field | Required | Notes |
|---|---|---|
| Organization name | yes | What appears at the top of the sidebar. You can rename it later in Settings → Organization. |
| Description | no | Short description shown to invited members. |
| Logo | no | PNG or SVG; you can add this later too. |
| Industry | no | Used for template suggestions. |
Click Continue.
Step 3, Path selection (/onboarding/path-selection)
Pick how this Flero instance will be used. This affects which defaults the next step seeds.
📸 Screenshot needed:
onboarding__path-selection.png, two large tiles side by side: SaaS / hosted and Self-hosted production, each with a short description.
| Path | Pick this if… |
|---|---|
| SaaS / hosted | You're on app.flero.ai (or your provider's hosted Flero) and don't manage the infrastructure yourself. |
| Self-hosted production | You're running Flero on your own infrastructure (Docker / Kubernetes / cloud). Triggers production-config defaults. |
Don't overthink this, every setting is editable later in Settings → Workspace / Organization.
Step 4, Production config (/onboarding/production-config)
Only shown if you picked Self-hosted production in step 3. Confirms the operational settings the platform should start with:
- Time zone, used for schedules and logs (defaults from your browser).
- Log retention, how long to keep execution history (default: 30 days).
- Default execution timeout, kills runaway nodes after this many seconds (default: 300).
- Sender email, used for system emails like invites and password resets.
Most teams accept the defaults and tune them later. Click Finish.
After onboarding
You're dropped at /workflows, the workflow list, with an empty state and a prompt to create your first workflow.
📸 Screenshot needed:
onboarding__empty-workflows.png, the workflow list immediately after onboarding, showing the empty state with the "Create your first workflow" CTA.
If you want a quick win, jump to Your first workflow →. If you'd like to look around first, Tour of the app → maps everything out.
Tips & gotchas
- Only the first user sees the wizard. Once onboarding is marked complete, subsequent sign-ups land directly on
/workflows(or/loginfor approval-pending accounts). - Re-running onboarding is possible from Settings → Organization → Re-run onboarding but rarely needed, every screen has an editable equivalent in Settings.
- Path selection isn't load-bearing. It only chooses defaults for the next step. You can switch a "SaaS" instance to "Self-hosted" defaults at any time.
Related
- Tour of the app, what each part of the sidebar does
- Organization settings, change anything onboarding set
- Inviting members, add teammates now that the org exists
Found something out of date? This page lives in the Flero docs content set.