The default organization is a different concept, consider it as the pre-existing organization in the system, but it's a separate organization from the others.
Say you manage the networks of two organizations which are using the captive page:
- University of Bangalore
- University of Rome
You'll have two configuration files, one for each, eg: bangalore.yml and rome.yml, default.yml will not be mentioned anymore.
But most of the configuration in both files is boilerplate (repeated code), if you delete everything and leave only what is different it won't work, but that's what we need.
We need an internal configuration definition which is used as default but can be overridden in the files of bangalore.yml and rome.yml.
The result we'll have is much leaner org config files and will also be easier to add new config without having to go over all the YAML to update them because they'll update themselves automatically.
There's one catch: it shall be possible to override/delete default values by passing empty objects for example.
Is it clearer now? If not please ask more detailed questions.