Domain
A Domain is a logical grouping of assets based on business, organizational, or operational boundaries. It lets you segment your asset data to reflect how your enterprise is structured — by department, business unit, region, or customer.
Think of a Domain as a container that holds related assets together so they can be managed, viewed, and governed as a unit.
Core concepts
Why Domains matter
Domains bring business context into your technical asset inventory. They let you:
- Organize assets by team, department, or geography — so Finance sees their servers and HR sees theirs
- Assign ownership and accountability to the teams responsible for each set of assets
- Support multi-tenancy by separating customer or division-specific assets
- Scope dashboards and reports to specific parts of the organization
- Enable access control so teams only see and manage what is relevant to them
Hierarchical Domains
Domains support parent-child relationships, enabling nested structures:
Company
├── Finance
│ ├── Finance_NorthAmerica
│ └── Finance_Europe
└── Engineering
├── Platform
└── Security
Each Domain at any level can contain Elements, and child Domains inherit organizational context from their parents.
Example
| Domain | Assets (Elements) |
|---|---|
Finance | Server_001, PayrollApp |
HR | Server_002, HR_DB |
Both sets of assets exist in the same registry, but by assigning them to different Domains they can be managed and visualized independently.
Built-in Domain
The Asset Registry ships with one built-in Domain:
| Domain | Description |
|---|---|
| Business Context | The root domain for the Canonical Business Context Model. Organizes all BCM-related elements including products, customers, and business impact assessments |
This domain is pre-configured and cannot be edited or deleted.
Creating a Domain
Navigate to Domains in the top navigation bar and click + New Domain.
Settings
| Toggle | Default | Description |
|---|---|---|
| Active | On | Whether the Domain is available for use |
| Built In | Off | Marks the Domain as system-defined. Built-in Domains cannot be edited or deleted |
Details
| Field | Type | Required | Description |
|---|---|---|---|
| Domain Name | Text | Yes | A unique name for this Domain. Duplicates are rejected with a validation error |
| Description | Text (multiline) | No | A brief explanation of what this Domain represents |
| Parent Domain | Dropdown | No | An optional parent for building hierarchical Domain structures (e.g., Finance > Finance_APAC). The dropdown excludes self and descendants to prevent circular references |
Viewing and editing
Click any row in the Domains table to open it in view mode. From there:
- Click the edit icon to switch to edit mode
- Click the delete icon to remove the Domain (with confirmation)
Built-in Domains display a warning banner and cannot be edited or deleted.
Best practices
- Use clear, meaningful names that reflect your organizational structure (e.g.,
Engineering_Platform,Customer_Acme) - Plan for hierarchy if you manage a global organization — start broad and refine with child Domains
- Audit Domain membership regularly to ensure assets stay correctly categorized as your organization evolves
- Leverage Domains for access control when integrating with role-based views and permissions