Workspaces

A workspace is your team's container for workflows, credentials, variables and executions. Everyone in a workspace works on the same workflows. Workspaces belong to an organization.

An organization holds one or more workspaces. Each workspace has its own workflows, credentials, variables and executions, and its own members, each with a role.

When to use one workspace vs many

Use one workspace per team or per environment. Common splits:

Per environment: Production and Staging, so a test never runs against production services.
Per team or business unit: each team keeps its own credentials and workflows.
Per client: when you build workflows for several customers who must stay separate.

The right size is "shared credentials, shared context". A workspace per workflow is too fine.

Workspace settings

Open Settings → Workspace. The tab always shows the workspace you are working in. It has these sections:

Section	What it holds	Who can change it
Your Workspaces	Every workspace you belong to, with your role in each and a Switch button	Anyone
General	Workspace name and description	Owner
Settings	Public Workflows and Require Approval switches	Owner
Policies & Quotas	Max Workflows per User and Max Executions per Hour	Owner
AI Budgets	Monthly AI spend limits. See AI budgets.	Owner
Members & Roles	Members, their roles and invite status	Owner and admins
Variables	Workspace variables, read with `{{ $env.NAME }}`	Owner and admins
Danger Zone	Delete Workspace	Owner only. Hidden from everyone else.

Admins see the General, Settings, Quotas and AI Budgets fields as editable, but only the owner can save them. An admin who saves gets an error.

The Settings and Policies & Quotas values are stored with the workspace. Flero does not enforce them yet.

Settings, Teams, Manage for the current workspace: Your Workspaces lists Operations and Workspace with Owner badges, followed by the General card with the workspace name and description fields.

Variables

Workspace variables hold values that many workflows share, such as an API base URL or a region.

Settings → Workspace → Variables → Add Variable.
Enter a Variable Name and a Value, and an optional Description.
Turn on Secret for values that should stay hidden, such as keys.
Save.

Use the variable in any expression field as {{ $env.NAME }}. If a workflow reads a variable that is not set, the node fails before it runs with Workspace variable "NAME" is not set.

To change a secret variable, enter a New Value. Leave it blank to keep the current value. Deleting a variable breaks every workflow that reads it.

Creating a workspace

Settings → Workspace → Your Workspaces → Create Workspace. Enter a Workspace Name and an optional Description, then click Create Workspace. You become its owner.

On Flero's hosted service, only Flero staff can create workspaces, so the button is hidden. Ask your Flero contact for a new workspace.

What's isolated between workspaces

Resource	Isolated per workspace?
Workflows, folders and executions	Yes
Workspace variables	Yes
Credentials with Personal or Workspace scope	Yes
Credentials with Organization scope	No. Organization members can use them in every workspace. See Credential scope.
AI budgets	Yes
User accounts	No. One account can belong to many workspaces, with a different role in each.

Deleting a workspace

Settings → Workspace → Danger Zone → Delete Workspace. Only the owner sees this section.

Deletion is permanent and cannot be undone. The workspace and its data are removed. There is no archive step for a workspace.

Tips & gotchas

Check the active workspace before you change anything. Settings, credentials and workflow lists all follow the workspace you are in.
To call a workflow in another workspace, give it a webhook trigger and call it with an HTTP Request node.
Webhook paths are shared across the instance. Two workspaces cannot both use /trigger/orders. Prefix paths with the team or workspace name.

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