2.2.3. Domain and Subdomain Configuration

💡 First Principle: Domains provide a governance layer above workspaces—like corporate policies that apply to entire departments. Without them, you'd need to configure the same security policies workspace by workspace, and inevitably something would be inconsistent. Domains let you say "all Finance workspaces must have these sensitivity labels" once, rather than repeating it in 20 places.

Scenario: The Finance department wants to ensure all their workspaces follow consistent security policies and data classification, but individual teams within Finance (Accounting, Treasury) need their own workspaces.

Domain Configuration Steps

1. Create Domain (Admin Portal → Domains)
2. Create Subdomains (optional, for deeper hierarchy)
3. Assign Workspaces to domains/subdomains
4. Configure Domain Settings (default policies, data owner)

Key Domain Settings

• Data Domain Owner: Responsible individual for the domain
• Contributors: Who can contribute to domain governance
• Default Policies: Sensitivity labels, endorsement requirements

⚠️ Exam Trap: Workspace-to-subdomain assignment is performed from Workspace Settings, not from the Admin Portal domain configuration. This trips up many test-takers who look in the wrong place.