Lightspeed Systems Mobile Manager is set up the same way your educational institution is set up, in a hierarchical fashion, which is part of what makes it such a powerful solution for schools. The top level is your Organization, followed by your Groups. Setting up your devices in this way gives you the most flexibility to configure your settings to work the way your organization works, allowing smaller groups down the hierarchical tree to be configured especially for their needs without affecting other groups.
Take a look at the inheritance
With the hierarchical setup, Mobile Manager sets policies via inheritance. By default, when you configure a setting, it automatically applies the setting to all the child groups beneath it. This allows for rapid configuration across your district, while still remaining agile, allowing individual groups to set up their own policies.
Similar to genetic inheritance, your groups are set up to inherit traits from their parent group and pass those settings on to their child groups. Unlike genetics, if you want to change the settings for a particular group, you can!
If you wish to impose settings on a group or groups, and thereby not allow them to alter the inherited configuration, you can easily lock the policy setting.
Devices can be in many groups at once. If, for example, as shown in the figure above, a device is in Group F it would inherit settings from Groups C and A. The device will only show a single group. This is because Mobile Manager will now compile all groups’ settings into a single profile for the device to make changes show on the devices faster.
Devices get the lowest settings on the tree. For example, if “Allow use of camera” is disabled in group A but is enabled in group G, then cameras will be enabled unless “Allow use of camera” is locked in group A.
When an administrator applies a restriction or allowance to a group, the users will pick up the nearest applicable policy on the hierarchical structure. If there is a conflicting change that has been made by two administrators at the same hierarchical level, then the most restrictive policy is applied.
In our demo environment, Southern Academy is the organization. Under the main organization, we have several groups, each composed of a different school.
Within each school, there are further groups. For example, Touring Magnet School has groups for individual classes, such as an English, Spanish, and Social Studies. These groups are Tier Three groups, proceeding Tier Two (Touring Magnet) and Tier One (Southern Academy).
These unique groups allow us to assign different settings (policies) to different groups based on the needs of the particular group. For example, we can give individuals within the Staff group less restricted access to various functions. This allows us to assign a certain set of more restrictive policies to students and another set of less restrictive policies to staff. You will learn more about policies in following lessons.
The following screenshots show the group structure of our demo organization as you navigate through the hierarchy. Click on the Group Switcher to open the hierarchy window and click on group names to navigate through the organization.
Click the arrow to select the group and make changes to the group (and sub-groups) as needed.
You’ll see the current group selected at the top of the interface next to the Group Switcher and you can navigate backward to higher groups by clicking on the group name in the hierarchy list.
With the hierarchical setup, Mobile Manager sets policies via inheritance. By default, when you configure a setting, it automatically applies the setting to all the child groups beneath it. This allows for rapid configuration across your district, while still remaining agile, allowing individual groups to set up their own policies. In other words, all settings (policies) that you have set for your Tier One group (Southern Academy) will automatically apply to all tiers under in (in this case, to Tier Two groups, which are the different schools, and all Tier Three groups, which, in the case of Touring Magnet School, are the various classes.) Just because policies are passed down from one tier to the other does not mean that each tier absolutely has to follow the policies of the previous one. You can assign individual policies to individual tiers that will override the inherited policies.
The following example illustrates the concept of inheritance.
Currently, we have the camera policy within Southern Academy, the Tier One organization, set to On and locked. (Policies will be explained in detail in Lesson 6.)
As a result, the policies in all Tier Two groups (and those in every following tier), are automatically set to have the “Allow use of camera” settings to On (and locked), inheriting the settings from the Tier One group.
Every single group within every single tier under each Tier Two group will also inherit this setting.