Our site uses cookies to improve your browsing experience. To learn more please read our Privacy Policy

Update: eSafety and Policies


Administrators can now configure the users' visibility and communication settings for a site – in itslearning, these settings are called eSafety. Some rules are configurable, while others cannot be edited.

In short, the settings decide:

  • who will find users in searches.
  • who users may communicate with.
  • who users may receive communication from.

With eSafety you can, for example, prevent learners from sending and receiving messages from staff at other schools.

eSafety is a profile setting managed from the Administration tab >> Profiles >> Edit profile.


Help icon Read more about eSafety in the help!


A policy is a collection of profile settings that can be assigned to profiles or individual users within an organisation – such as a site or school. Policies override the default profile or user settings. You are allowed to combine settings of different types in a policy, as well as assign multiple policies to a profile or user.

With the introduction of policies, you no longer have to edit existing profiles or create new profiles if you want to change the permissions for a set of users. This creates a more flexible system, allowing schools to have their own rules, independently from the rest of the site's schools.


How does it work?

Let's use an example to illustrate the usage. In a hierarchy with four schools – Chesterson, Springfield, Whitneyville, and Enfield – Chesterson has experienced that a group of pupils have been bullying others through the internal messaging system.

To put an end to this, the headmistress at Chesterson decides to turn off internal messages for all pupils. She asks the system administrator to disable the messaging system for the Pupil profile, but he is reluctant. He points out that editing the profile would disable the messaging system for all pupils in all four schools, and, knowing how extensively the messaging system is used by the other schools in the hierarchy, he argues that this is a really bad idea.

Instead, the system administrator asks the headmistress to consider using policies. He argues that the best option is to create a policy and assign the policy to the Pupil profile at Chesterson or – optionally – to individual pupils of the school. The last option would efficiently prevent only misbehaving pupils from using the messaging system. The headmistress agrees, and, instead of blocking the messaging system from all pupils at Chesterson, Springfield, Whitneyville, and Enfield, the administrator simply suspends the privilege for four individual pupils at Chesterson School.

Help icon Read more about policies in the help!

Important about hierarchies and the new functionality

In order to allow adding terms, policies and eSafety rules, the root hierarchy should be defined as a site. The organisations for which you want to add terms, policies and eSafety rules must be defined as schools or sites. You should not add a site under a site. The logical rule is: one site, and several schools within that site, but not several schools within a school.

Hierarchies are edited from Administration >> Hierarchy. Select the correct type from the Hierarchy type drop-down list, and click Save.


No comments (Add your own)

Add a New Comment


Comment Guidelines: No HTML is allowed. Off-topic or inappropriate comments will be edited or deleted. Thanks.

Webinars Video Overview Contact Us