In this section: |
Defaults streamline device management and capture workflow because they:
Passing these settings down is referred to as inheritance. Because objects inherit settings from the defaults, you do not have to set them manually. This simplifies tasks such adding a new device or creating a new schedule.
Set the defaults during installation or when upgrading to get the full benefit of this efficiency. |
As you work with defaults, understand these concepts.
These rules also apply:
Defaults are set in different ways, depending on the object.
These defaults replace the global defaults in earlier releases. |
If your EchoSystem Server (ESS) has a hierarchy of parent and child organizations, the inheritance chain has four levels for most objects:
If you do not implement delegated administration (and therefore do not have a parent-child hierarchy), the chain has three levels: Level 2, the child organization level, is eliminated. Objects or sections inherit settings directly from the parent organization.
This inheritance chain does not apply to devices, which inherit their settings directly from the device default settings.
For the most part, system settings are not inherited. One exception is the Academic Staff Upload Properties, which are set at a system level (System > System Settings), then inherited by individual Academic Staff.
When you change an object's organization, the object's properties may not inherit as expected.
An object's properties will be handled in these ways:
No customization rule. If the object's properties have not been customized, it has the default values of its parent. When you move the object to a new organization it inherits the default properties of its new parent.
Room 667 was owned by Echo360 University. The Administrator of Echo360 University did not change the Admin User Name for the Ad Hoc Interface (capture appliance) from the default value. It is Admin. Now you move Room 667, giving ownership to the engineering school. The engineering school has also preserved the default value of this setting. After moving, the value remains Admin. |
Customization rule. If the object has a customized property, the customized property is preserved when the object is moved to a new organization.
Room 667 was owned by the law school, which customized the Admin User Name to Judge. Now you move Room 667, making it part of the engineering school. The Admin User name remains Judge. If the engineering school has a different Admin User Name (Admin, Design), you will have to change the Admin User Name for Room 667 in the ESS interface, by navigating to the room details page for Room 667. |
The customization rule does not apply if you specify the value of a property on a spreadsheet and import the property using the import/export method; the value on the spreadsheet overrides any other value.