Organizations and tenancy model

IBEE Solutions uses a two-level tenancy model: organizations contain workspaces, and workspaces contain resources. Billing, team management, and access controls live at the organization level, while compute, storage, and networking resources are scoped to individual workspaces.

Tenancy hierarchy

Account (your login)
└── Organization (billing, team, API tokens)
    └── Workspace (VMs, storage, networking, firewalls)

• Account — your login identity. One account can own or be a member of multiple organizations.
• Organization — the billing and administrative boundary. Each organization has its own wallet, payment method, invoices, team members, API tokens, and activity logs.
• Workspace — the resource boundary within an organization. VMs, block storage volumes, object storage buckets, firewalls, load balancers, DNS zones, and other infrastructure resources belong to a workspace.

What lives where

URL structure

The portal URL reflects the tenancy model:

Creating an organization

See Create an organization for the step-by-step process. Each organization requires a name, account type (Business or Individual), billing address, and currency.

Switching organizations

Use the organization switcher dropdown in the top navigation bar to move between organizations. You can also return to the Organizations page and select a different card.

Workspaces

When you open an organization, you land on the Workspaces page. Select a workspace to access its resources. Resources like VMs, storage, and networking are scoped to the active workspace.

Organization-level concerns — billing, team, API tokens, and activity logs — are always accessible from the sidebar regardless of which workspace is active.

Billing scope

Billing is aggregated at the organization level. All resources across all workspaces in an organization share the same wallet balance, payment method, and invoices. Usage limits and quotas also apply at the organization level.

Before creating resources (VMs, block storage volumes), the platform checks the organization’s billing state. If the wallet balance is insufficient or billing is suspended, a billing-blocked popup prompts you to add credits before proceeding.

Best practices

• Use one organization per billing entity — each organization gets its own invoices and payment method.
• Use workspaces to separate environments — for example, production, staging, and development workspaces within a single organization.
• Assign least-privilege roles to team members at the organization level.
• Use API tokens scoped to the organization for automation and CI/CD.

Related pages

• Create an organization
• Billing and usage
• IAM
• Dashboard