Search all guides
Documentation / Core Concepts
Ownership protects existing configuration
An object that looks compatible is not automatically an object DOMAINTAINS is allowed to change.
Record verified creation
The ownership ledger records native FreePBX object identities and configuration fingerprints only after creation has been verified. Trunks, routes and number configuration outside that authority remain protected. Exactly matching unowned objects may be reused, but reuse does not confer ownership.
Reject drift
Reconciliation checks the current configuration against recorded ownership evidence. Unexpected administrator changes fail closed rather than being silently overwritten or adopted. A provider-authorised change can be applied when the existing owned object still matches its recorded fingerprint.
Adopt only after review
Safe legacy configuration can require explicit administrator-confirmed adoption. Conflicting or ambiguous objects cannot be adopted. Do not delete the ownership ledger or recreate trunks to bypass a conflict; preserve native identities and inspect the diagnostic first.
Configuration protection / four cases
A matching name
is not permission.
What matters is verified ownership and the actual configuration, not whether an object looks familiar.
Manage after verification
Ownership is recorded only after creation has been verified. Later changes require the current object to match the recorded evidence and the new configuration to remain provider-authorised.
Review eligible adoption interactively
fwconsole domaintains adoptWhat may happen to each object?
| Actual state | Permitted outcome | Forbidden shortcut |
|---|---|---|
| New and verified after creation | Record native identity and fingerprint as owned | Recording ownership before creation is verified |
| Unowned and exactly matching | Reuse without mutation or ownership capture | Normalising, deleting or recreating it |
| Owned and fingerprint matches | Apply a provider-authorised change and verify | Ignoring current provider authority |
| Owned but unexpectedly changed | Stop and preserve the conflict | Recapturing the new fingerprint to erase the conflict |
| Safe legacy object with reviewed plan | Explicit administrator-confirmed adoption | Adopting an ambiguous or foreign object |