Skip to content
Docs
flero.ai

Workspaces

A workspace is your team's container for workflows, credentials, and executions. Multiple users share a workspace; everything inside it is collaborative.

Above the workspace sits the organization, a top-level container that owns one or more workspaces (enterprise plans).

Organization
├── Workspace A     ← workflows, credentials, executions live here
│   ├── members
│   ├── credentials
│   ├── workflows
│   └── executions
└── Workspace B
    └── …

When to use one workspace vs many

One workspace per team or business unit. Common splits:

  • One per environment, Production, Staging, Development. Avoids accidentally running a workflow against the wrong service.
  • One per product line, Acme Tools, Acme Software, …
  • One per tenant, if you serve customers and each customer has their own workflows in isolation.

Don't create a workspace per workflow, that's overkill. The granularity is "shared context, shared credentials".

Creating a workspace

From the sidebar profile popup → Create workspace:

  1. Name, what teammates will see.
  2. Description, optional.
  3. Icon, optional image.
  4. Time zone, defaults for schedules.

Click Create. You're switched into the new workspace as the owner. It starts empty.

If you don't see Create workspace in your profile popup, your role doesn't allow it, only owners and admins of the organization can create new workspaces.

Workspace settings

Manage under Settings → Workspace (with the workspace selected). Tabs:

  • General, name, description, icon, time zone, default execution timeout.
  • Members, invite, change roles, remove.
  • Credentials, same as the top-level Credentials screen, filtered to this workspace.
  • Variables, $env.VAR_NAME workspace-level environment variables.
  • Alerts, auto-Slack on workflow failures, etc.
  • Storage, file-storage backend configuration.
  • Audit log, who did what when.
  • Workers, for self-hosted: which worker pools serve this workspace.
  • Danger zone, archive, transfer, delete.

What's isolated between workspaces

Resource Isolated?
Workflows ✅
Workflow executions ✅
Credentials with Personal or Workspace scope ✅
Credentials with Organization scope ❌ shared across org
Templates with Workspace visibility ✅
Templates with Organization visibility ❌ shared
Environment variables ($env.*) ✅
User accounts shared at the user level, same user can be in multiple workspaces, each with their own role
Billing depends on plan, usually per-organization, occasionally per-workspace

Archiving / deleting a workspace

Settings → Workspace → Danger zone.

  • Archive, read-only. Workflows visible, can't be run or edited. Reversible.
  • Delete, permanent. 30-day grace period before data is purged.

Both require typing the workspace name to confirm. Both record an audit event.

Tips & gotchas

  • Resource limits scale per workspace on most plans. Two workspaces is two budgets; one workspace is one. Plan accordingly.
  • Cross-workspace references aren't possible. A workflow in Workspace A can't directly invoke a workflow in Workspace B; expose the second workflow as an API and call it via HTTP, or use a Sub-Workflow only within the same workspace.
  • Workspace time zone affects schedules unless individual triggers override.
  • Workspace deletion is irreversible after 30 days, there's no "support, please restore my data" path. Be sure.

Found something out of date? This page lives in the Flero docs content set.