Overview

Define organisations, groups, and workspaces to organise your resources. Taxonomy gives you a single console to structure your platform into a clean hierarchy, where workspaces are the boundary that every other service scopes its resources to, so your teams, environments, and projects stay isolated and easy to govern.

An organisation sits at the top. Inside it, groups act as folders that can nest to any depth, and workspaces hold the actual resources, either directly under the organisation or within a group. You can reorganise as you grow: a move re-parents a workspace or a group without recreating it. Access bindings attach at any level, organisation, group, or workspace, so you govern broadly or narrowly from the same hierarchy.

Core resources

Organisations: the top-level container. Each one has an owner, an identity from IAM, and holds every group and workspace beneath it.
Groups: folders that organise workspaces within an organisation. A group can nest inside another group, so you can model whatever structure your teams need.
Workspaces: the isolation boundary every other service scopes its resources to. A workspace belongs to an organisation and can sit at its top level or inside a group.
Operations: creating, updating, deleting, or moving a resource returns an operation record that comes back already completed.

Get started

Create an organisation and workspace Set up the hierarchy your resources live in.

Resource hierarchy How organisations, groups, and workspaces relate.

Use cases

Reference architectures

Training and tutorials

IAM Access bindings scope to a workspace, group, or organisation.

Compute VMs are created inside a workspace.

Storage Buckets are scoped to a workspace.

API standards The resource-oriented API every service shares.