Glossary

One term, one meaning — identical across database, code, API, and UI (ADR 0040). The table below is the single source of truth. See also the Workspaces and Organizations explanation page for the conceptual model.

Term	Meaning	Notes
Organization	The top-level billing tenant. Owns seats, SSO configuration, and invitations. A user belongs to exactly one organization.	DB: organizations. Kind is personal or team (the team value’s user-facing label is “Organisation”).
Workspace	A resource container inside an organization. Holds projects, tasks, workflows, runs, secrets, connectors, schedules, and API tokens. Membership is per-user.	DB: workspaces, FK workspace_id. The word “team” is not used for this concept.
Project	A named unit of work inside a workspace. Groups tasks, issues, workflows, and git/tracker credentials.	DB: projects.
Task	A single agent execution launched against a project. Tracks cost, duration, events, and outcome. A task is the unit you follow, logs, intervene, or cancel.	DB: tasks.
Run	One execution instance of a workflow. A workflow can produce many runs over time.	DB: runs.
Workflow	A declarative DAG of nodes (code, db_query, connector, human, …) that executes as a run. Storable, versionable, and triggerable on a schedule or webhook.	DB: workflows.
Agent	A Claude Code process spawned by SupaCloud to carry out a task. Communicates back through MCP tools.	Configured via an Agent Profile.
Agent Profile	A saved configuration for an agent: model, allowed MCP tiers, pre/post-flight checks, execution mode. Applies to tasks by default when set as the workspace default.	DB: agent_profiles.
Teammates	A multi-agent group spawned for a single task. “Team” in this context refers strictly to agents, never to the tenant.	Config keys: agent_teams / max_teammates.
Connector	A Wasm Component (WASI 0.2) that wraps a third-party API or service. Installed from the marketplace or custom-built; executed by the connector executor.	DB: marketplace_items (kind='node').
Runner	A decoupled worker node registered to the SupaCloud hub (instance-global, system-admin managed; not scoped to a workspace). Executes tasks and, optionally, connector workloads dispatched by the runner fleet.	DB: runners.
Schedule	A cron-based trigger attached to a workflow or task template. Managed via schedule add/pause/resume/delete in the web terminal.	DB: task_schedules.
Resource	A named, credential-backed integration (SMTP server, Telegram bot, webhook endpoint, Discord bot, database connection, …) available inside a workspace.	DB: resources.
Delivery board	The agent-profile overview page at /delivery. Shows live work grouped by profile and delivery state. Not a tenant concept.	Route: /delivery; i18n namespace: delivery_board_*.
Backlog	An automatically maintained queue of prioritized work items derived from a project’s issue tracker. Managed by the autonomous backlog mode (ADR 0039).	DB: backlog_items.
Concept approval mode	An autodev approval mode where the agent first produces a code-grounded implementation concept for human review, then implements it on approval — within a single run.	Value concept of project_automations.approval_mode.
Completion action	A per-automation setting for what happens to a linked issue when an issue-linked task finishes: close (comment and close/transition), comment (comment but leave open), or nothing (neither).	Column project_automations.completion_action.
Marketplace	The catalog of installable primitives: workflows, scripts, connectors, and bundles. Items can be free or paid and are published by verified creators.
MCP	Model Context Protocol — the tool interface between SupaCloud and the agent process. Exposes supacloud.* tools at four access tiers (baseline, read, ops, deploy).