An Organisation is the top-level workspace in dFlow.

It is the boundary for billing (on dFlow Cloud), team members, invites, and shared integrations (Git providers, registries, cloud accounts) that your Applications use.

“Tenant” vs Organisation

Documentation and APIs sometimes say tenant for the same isolation boundary the dashboard labels Organisation. When you read about tenant-scoped access or multi-tenant behavior, interpret it as your Organisation unless the page states otherwise.

What lives inside an Organisation

• Applications (and legacy Projects during ): what you ship.
• Worker Nodes and connection assets such as SSH keys used to reach your compute.
• Team membership and roles that control who can change what.

Nothing in dFlow spans Organisations: each one is a separate account workspace.

How this connects to the product model

Under an Organisation you model work as Application → Environment → Service → Deployment. The Organisation does not replace those layers; it owns them. Read How dFlow is structured for the full map.

See also

• Tenant access model: RBAC and permissions.
• Invites and team members: adding people to your Organisation.
• Legacy Projects vs Applications: if you still use the legacy hub.