Spaces

Spaces group stacks into a tree, by team, environment, project or any other criterion. Every organization starts with a Root space; you create child spaces under it, up to five levels deep. A stack belongs to exactly one space, chosen in the wizard's Basic Info step; it cannot be moved afterwards.

Creating, editing and deleting spaces requires the Write role.

What a space scopes

• Bundles: a stack can attach configuration bundles from its own space, and from ancestor spaces when Inherit bundles from parent is enabled on every space along the way. That switch governs bundles only.
• Cloud integrations: an AWS integration can be attached to stacks in its own space and in that space's children.

Spaces do not restrict which members can see or change a stack; roles are organization-wide (see Identity & Access).

Creating a space

Spaces > Create Space asks for:

• Name.
• Slug: a URL-friendly identifier (lowercase, hyphens only), filled in from the name until you type your own.
• Description (Optional).
• Parent Space: the space this one goes under. Every space you create needs a parent; pick the Root space for a top-level one. The dialog's default entry, Root (no parent), sends no parent and is refused by the API.
• Inherit bundles from parent: automatically offer bundles from the parent space to stacks in this one.

Edit changes the name, slug, description and the inheritance switch. The parent cannot be changed after creation.

Viewing spaces

The Spaces page has two views. The Tree table lists each space's Name, ID (the slug) and Inherit (Yes / No) with its actions. The Graph draws the hierarchy under a synthetic Organization root; clicking a node opens a sheet with the space's parent, depth, number of direct children, bundle inheritance and ID, and the same actions.

Deleting a space

Delete on a space is refused while the space still contains stacks or child spaces; delete those first (stacks cannot be moved to another space). The Root space has no Delete action in the UI.