Organizations

Model your business as a hierarchy of organizations, each with its own scoped costs, users, and billing configuration

4 minute read

Sub-organizations can mirror your internal business units, or, for managed service providers and resellers, the customers you manage. Browse and create organizations in a hierarchy, then configure each one:

Scope rules: Define which cloud resources belong to each sub-organization by filtering on billing dimensions.
Billing configuration: Attach billing rulesets that control how costs are re-rated for an organization.

Access the Organizations page

Log in to the CloudBolt Platform.
In the sidebar, select Settings.
Select Organizations.

Viewing the page requires organization-admin visibility. The Create Organization button and scope-rule editing additionally require the Owner permission.

Organizations overview

The page is split into two columns: an expandable organization tree on the left, and a detail panel on the right showing the selected organization. The tree shows your current organization and its descendants only.

Section	Description
Organization tree	An expandable, hierarchical view of your current organization and its descendants, showing parent and child relationships.
Detail panel	Tabs with the details and settings of the organization selected in the tree.
Create Organization	A button to add a new organization and place it within the hierarchy. Requires the Owner permission.

The detail panel contains the following tabs:

Tab	Description
General	Always available. Shows the setup checklist, the organization’s parent and children, and organization actions.
Billing	Shown when the organization is linked to a managed tenant. Assign and detach billing rulesets.
Custom Variables	Shown when the organization is linked to a managed tenant. Custom variables referenced by the organization’s billing rulesets.

Create an organization

Select Create Organization.
In the dialog, enter a Name for the new organization.
Choose a Parent Organization. The root organization is selected by default.
Confirm the dialog to create the organization.

Organization names must be unique. If the name is already in use, the dialog shows “An organization with this name already exists.”

General tab

The General tab summarizes the selected organization:

Setup checklist: New organizations show a checklist of setup steps (Organization created, Enable authentication, and Define scope rules) so you can see what remains before the organization is fully operational.
Hierarchy: Chips show the organization’s parent and its child organizations.
Root organization: When the root organization is selected, a note explains that it sees all data connected to the tenant.
Actions: Administrators can select Join This Org to gain access to the organization, or Switch to {name} to make it their active context. See Switch Organization.

Scope rules

A scope rule defines which cloud resources belong to a sub-organization by filtering on billing dimensions. Together, an organization’s scope rules determine which accounts, and therefore which costs, appear in that organization’s dashboards and reports.

Scope rules are edited by an administrator from the organization’s immediate parent. Each rule consists of three parts:

Part	Description
Dimension	The billing dimension to filter on: Billing Account Name, Billing Account ID, Sub Account Name, Sub Account ID, Provider, or Azure Customer/Reseller Name or ID.
Operator	How the values are matched: equals, in, contains, does not contain, or matches regex.
Values	The values to match. For equals and in, you pick from actual values found in your billing data; the other operators accept free text.

Rules are joined with AND/OR. Select Add Rule to add more rows, and Save Scope Rules to save the whole set. The set is saved atomically: if a save fails, the organization’s previous rules are left untouched.

The server blocks two kinds of invalid saves:

Overlapping scope: Rules that overlap with a sibling organization’s scope are rejected with “Adjust the highlighted rule so each sub-organization resolves to a distinct set of accounts”.
No matching data: Rules that match no billing data are rejected.

On a successful save, the platform confirms “Scope rules saved — sub-organization data updates on the next pipeline run.” Data moves to the sub-organization on the next pipeline run.

Billing tab

The Billing tab is shown when the organization is linked to a managed tenant. Select Assign Ruleset to attach a billing ruleset to the organization. The ruleset defines how costs are re-rated for this organization. Assigned rulesets show their rule, metric, and variable counts and can be detached from the organization; detaching removes the assignment but keeps the ruleset itself.

A banner warns when assigned rulesets reference custom variables that are not yet defined for the organization.

For details on creating and managing rulesets, see Billing Rulesets.