Before you start using eSafety, policies and terms it is important to make sure that the hierarchies are correctly set up. Recently we introduced a setting called Hierarchy type in Administration >> Hierarchy >> Add/Edit hierarchy. This setting is crucial in order to make eSafety, terms, and policies work. The hierarchy type drop-down list has five options: Not defined, Site, School, Class and Group.
It is important to define the root hierarchy as a Site. You should not add a site under a site. The organisations for which you want to add terms, policies and eSafety rules must be defined as School or Site. The logical rule is: one site, and several schools within that site, but not several schools within a school. In the example below Downhill LA is the root hierarchy and has the hierarchy type Site. The schools below – Chesterson and Enfield – are added as schools.
If schools have sub-hierarchies, for example classes, they should have the hierarchy type Class, while groups within the class should have the Group hierarchy type. When the hierarchies are set up with the correct hierarchy type as illustrated below, eSafety, policies and terms should work.
Note: Below a hierarchy defined as School you can have hierarchies defined as Class, Group, and Not defined.
Read more about eSafety, policies and terms in the help!
Posted on Wed, January 20, 2010
by Øyvind Flatnes