Your customers create workspaces inside it. Each workspace keeps its own members, flows, connections, AI accounts, agents, prompts, skills, knowledge bases, MCP servers, approvals, usage, and subscription.
| Layer | Managed by | Examples |
|---|---|---|
| Platform | Site owner and administrators | Branding, mail, queues, storage, security, OAuth apps, AI defaults, payment processors, plans, system health. |
| Workspace | Workspace owner and permitted members | Integrations, AI accounts, agents, prompts, knowledge, MCP servers, workflows, runs, approvals, team. |
| Workflow runtime | JustFlows services | Trigger intake, queued execution, waits, approvals, tool calls, retries, logs, usage accounting. |
A flow becomes runnable when it has a valid trigger, connected nodes, any required workspace credentials, and a published version. Editing a draft does not silently change the currently published version.