A domain's configuration is what its on-chain record (its IID document) says about it: who controls it, which services and resources it exposes, what it is entitled to do, which claims are linked to it, and which other domains it relates to. The record is anchored by the domain's DID.
Read this page to understand the data model before you create or update a domain. For the full list of a domain's parts, see Core concepts. For the messages that change a record, see Domain settings.
What the record holds
| Part | What it says |
|---|---|
| Controllers | Who may update the domain's record and delegate permissions |
| Services | The endpoints the domain exposes |
| Linked resources | The documents and data the domain anchors |
| Accorded rights | What the domain is entitled to do, mainly expressed as UCAN parent capability documents |
| Linked claims | The claim types and collections attached to the domain |
| Linked entities | Links to other domains, which place this one in a graph of relationships |
The record is one part of a domain. The domain also has an ownable entity at its core, owner accounts, an optional governance group, a Matrix space and a VFS. A domain and its entity are not the same thing: Manage entities covers the entity.
Inheriting from a protocol
A domain can inherit properties from the protocol it was created from. When a property is set both on the protocol and on the domain, the domain's own value takes precedence. Digital twin domains explains how protocols act as templates.