Skip to main content
A workspace is the top-level boundary in CelerFlow. Everything you build — workflows, connections, and run history — lives inside one workspace and is shared with your team.

What a workspace is

In the database each workspace is a single row in agent_fleets, accessed via a [slug] segment in the URL (e.g. /{slug}/workflow/new). The slug is derived from the workspace name. The shorthand /~/... resolves to your first workspace and redirects to its slug, so links don’t have to hardcode it. A workspace is bound to exactly one team. Every team member sees the same workflows, connections, and run history. Access is controlled by role — see Teams & roles for details.

Creating your first workspace

When you sign in for the first time, CelerFlow walks you through a short onboarding flow:
1

Pick a use case

Choose the category that best describes what your team automates (research, outreach, reporting, etc.).
2

Name the workspace

Give it a short, memorable name — this becomes your slug.
3

Done

Your workspace is ready. The default platform agents are automatically seeded into your team’s agent pool so the Planner can start assembling workflows immediately.

Switching workspaces

Use the workspace picker in the top navigation bar to switch between workspaces. If you belong to multiple teams — say, a personal workspace and a company one — each appears in the picker. Clicking a workspace switches all context: workflows, connections, runs, and settings.
Platform agents are seeded once per workspace at creation time. Each workspace gets its own independent pool.

What’s shared inside a workspace

For connection details see Connections. For workflow building see Planner.