Multi-tenancy & account hierarchy

Root and tenant accounts

VMease organises everything into a tree of accounts, from a root account down to its tenants.

• The root (parent) account sits at the top; tenant (child) accounts are created beneath it and can, in turn, have their own tenants.
• Delegation flows top-down: a parent provisions tenants, assigns them resources, and sets the limits they operate within.
• A parent account can see itself and all of its descendants; a tenant sees only its own resources and users.
• Create and manage tenants under Multi-tenancy → Tenants.

Account context & switching

You always work inside one account at a time — your current context.

• Root users switch down into a tenant to administer it; while switched in, you see and act as that tenant.
• Use Exit Account (Account menu) to step back up to your own account.
• Your current account context, together with your role, determines everything on screen — the resources listed and the actions offered.
• Root-only areas (the Platform section) are not available while you are switched into a tenant.

What a tenant can consume (quotas)

Quotas are how a parent caps how much of each resource a tenant is allowed to use.

• A tenant can be given quotas limiting resources such as CPU, memory, storage and VM count.
• A tenant can never exceed its parent's remaining capacity — delegation cannot hand out more than the parent has left.
• A quota left at 0 or unset means unlimited (bounded only by the parent's own capacity), not zero.
• Set and review tenant quotas under Organisation → Quotas; see the Quotas explained (click here) concept for the details.

Sharing resources with tenants

Some resources are created by a parent and made available to its tenants rather than owned outright by the tenant.

• Shared resources are assigned from a parent down to a tenant, so the tenant can use them without owning or managing the underlying object.
• This lets a parent offer common infrastructure (for example networks or images) while keeping control at the parent level.
• Assignment follows the same top-down direction as the rest of delegation — parent to tenant, never the reverse.
• Review and manage what is shared under Multi-tenancy → Shared Resources.