Domain

In the KScope Asset Registry, a Domain is a logical grouping of assets (called Elements) based on business, organizational, or operational boundaries. It helps you segment and organize your asset data in a way that reflects how your enterprise is structured — such as by department, business unit, region, or even customer.

Think of a Domain as a container that holds related assets together so they can be managed, viewed, and governed as a unit.

---

🧱 Why Domains Matter

Domains provide context and control over your asset data. They help you:

• Organize assets based on business relevance (e.g., Finance vs. HR)

• Assign ownership and accountability to teams or departments

• Support multi-tenancy by separating customer or division-specific assets

• Apply policies, filters, and views based on logical asset groupings

• Enable secure access control, so teams only see and manage what’s relevant to them

---

🧩 Example: Using Domains in Practice

Let’s say your organization has two departments — Finance and HR — each with their own servers, apps, and databases. You want to keep their assets logically and operationally separated.

Domain	Assets (Elements)
Finance	Server_001, PayrollApp
HR	Server_002, HR_DB

Each of these assets exists in the same registry, but by assigning them to different Domains, they can be managed and visualized independently.

---

🔍 Key Characteristics of a Domain

Feature	Explanation
Logical Grouping	Groups Elements (assets) for organizational or business purposes
One-to-Many Mapping	A single Domain can contain many Elements, but each Element belongs to only one Domain
Hierarchical Support	Domains can be nested — for example, Finance → Finance_NorthAmerica, Finance_Europe
Access & Segmentation	Useful for scoping data views, reports, and permissions

---

🧭 Where Domains Fit in the Modeling Framework

In KScope Asset Registry:

• Each Element (asset) must belong to exactly one Domain

• Domains are independent of asset type or source — a Domain can contain servers, apps, or databases from any system

• Domains may have parent-child relationships, supporting complex structures like company divisions, geographic regions, or customer hierarchies

---

🔄 Example: Domain Assignment in Full Context

Element: PayrollApp
Element Type: Application
Domain: Finance
Module: ServiceNow
Attributes:
  - name: PayrollApp
  - version: 2.1
  - owner: Finance Dept

This shows that the PayrollApp asset is:

• Classified as an Application (via Element Type)

• Belongs to the Finance Domain

• Was imported from ServiceNow

---

🛠 When Would I Create or Use Domains?

You’d use or create Domains when:

• You want to segregate assets by team, function, or customer

• You’re managing assets for multiple tenants or subsidiaries

• You need to apply filters or access rules based on business structure

• You want to organize dashboards, queries, or reports around business units

---

💡 Tips for Managing Domains

• Use clear, meaningful names (e.g., R&D_APAC, Customer_ABC) for better traceability.

• Plan for hierarchy if you manage a global organization or multiple clients.

• Use Domains as a key access control layer when integrating with role-based views.

• Regularly audit Domain membership to ensure assets are properly categorized.

---

✅ Summary

A Domain in the KScope Asset Registry is your way to bring business context into your asset inventory. It allows you to organize, segment, and secure your data in ways that reflect your real-world structure.

Whether you're separating departments, divisions, customers, or tenants, Domains help you scale your asset registry without losing clarity or control.