Administrative levels


In order to cater for hierarchical groupings of schools, Airhead is split into a number of administrative levels as follows: 


- Deployment – this is an entire Airhead hosting instance

- Tenant – this is a business concept, i.e. the entity that pays the subscription 

- Authority – this is designed to cater for a whole Local Authority or district

- Cluster / Federation – this caters for groupings of schools

- Establishment – this is the school level


An Administrator can be created at each of these levels and the settings they control flow down the hierarchy. An Administrator of a higher level can choose whether  Administrators of levels below can override settings or not. When an Administrator selects ‘Settings’, they see tabs for the levels that they have control over. 



Usually you will be an Establishment Administrator and, apart from Personal Settings, this is the only settings tab you will see. 


There is no limit to the number of Administrators that can be appointed but they can only be upgraded to the Administrator level when they have logged into Airhead once. At this point, the user to be promoted needs to provide their profile ID to Airhead Education and confirmation of what level in the hierarchy they are to administer if there is a choice (usually it will be Establishment). 


Roles


There are six roles that Administrators may assign to users and within which they can define differentiated settings: 


- Pupil

- Early years

- Teaching Staff

- Non-teaching Staff

- Parent

- Other


Administrative settings


Within each administrative level, there are six areas over which the Administrator can exert control: 


- Groups

- Permissions

- Tiles

- Widgets

- Default launchpads

- Default flightdecks


Groups settings


snip20141003_22.png


Groups settings offers you the ability to view and synchronise information from group providers. Groups are used in the sharing of launchpads and flightdecks. There are currently two group providers in Airhead: 


- Airhead Groups – groups defined by membership of Airhead roles

- Google Groups – groups synchronised with your Google Apps domain


Clicking on the ‘View groups’ button for Airhead Groups reveals a list of the role groups as below (with your establishment name in place of Airhead Corporate School): 



snip20141003_23.png


Clicking on individual Airhead role groups will reveal the user names and email addresses of individuals in that group as below. 





Clicking on the ‘View groups’ button for Google Groups reveals a list of your domain’s Google groups as below:





Again, clicking on individual Google Groups will reveal the user names and email addresses of individuals in that group. Group members who have never logged into Airhead will display as email addresses only (no user name). 


You will also notice a ‘Synchronise’ button. Pressing this button will update the information we hold about your Google groups. Whenever you make changes to Google groups (add, remove or edit groups or users in those groups), you will need to synchronise them in Airhead. 


NOTE: When you first join Airhead, this button will read: ‘Never synchronised’. As an Administrator, one of your first tasks is to synchronise your groups with Airhead. 


Permissions settings


Permissions can be set differentially for different roles. Select the role from the dropdown box. If you click the ‘Override’ button and you have permission, you will be able to set the permissions applicable to the selected role for your Establishment:



 

The following permissions may be set:


- General

- LaunchPads

- FlightDecks

- Users and groups

- Inheritance


General – the Administrator can determine what theme is applied to Airhead by default and whether or not users can set their own theme. 




LaunchPads and FlightDecks – the Administrator can determine whether a user has permission to use LaunchPads, publish tiles and share launchpads. The Administrator can also determine whether a user has permission to use FlightDecks and share flightdecks with individuals and groups.



 

Users and groups – the Administrator can determine the scope of sharing for each role, i.e. at what level (and below) users can share. 




The Administrator may determine whether any of these settings may be overridden by an Administrator in a lower level in the hierarchy by clicking the ‘Inheritance’ button. 




Tiles settings


The Administrator can create tiles, edit tiles and set permissions on tiles. In the ‘Tiles’ settings, there are two tabs: 


- Shared with us – tiles that are shared with this level in the hierarchy

- Created by us – tiles that have been created by this level in the hierarchy





Click on the ‘Options’ button next to a tile to access the options for an individual tile.


Shared with us – the Administrator does not ‘own’ these tiles but can set permissions on them as follows: ]


- This tile is available to everyone

- This tile is available only to selected roles

- This tile is not available for any role

- This tile is available at any location

- This tile is available only at the school location

- This tile is available except at the school location

- This tile is not available at any location


This is the mechanism by which Administrators can remove offensive tiles from view or restrict access to them by role and location. 


The ‘Override’ button provides the same functionality as previously described.


If the tile is an auto-logon tile, the Administrator can set a user name and password that cannot be overridden, so that all users can access the resource with the single, specified account. This is known as a universal auto-logon tile. 

Even if the tile is not an auto-logon tile, the Administrator can still set a universal user name and password as a prompt. 


Created by us – the Administrator has more control over tiles that have been created by the level in the hierarchy over which they have administrative rights. 



The Administrator can:


- Delete the tile by clicking on the ‘bin’ icon

- Create a tile by clicking on the ‘Create tile’ button, including

o configuring the tile to be an auto-logon tile if it is a compatible service

- Edit the tile by clicking on the Options button, including

o Publish the tile, i.e. share it

o Set permissions on the tile (as described above)


Configuring auto-logon tiles


As an Administrator you can create a tile in exactly the same way as a normal user. An Administrator does have access to additional functionality and that is the ability to configure auto-logon tiles, assuming the target service will support it. 

When the Administrator either clicks on ‘Options’ or ‘Create tile’ in the ‘Created by us’ tab of the tile settings, there is an option to tick a box labelled ‘Enable auto-logons for this tile’. Once ticked, additional field are revealed which, when correctly completed, will support auto-logon for compatible services. 


How do I configure an auto-logon tile?


In order to configure an auto-logon tile, you will need some specific information about the way in which the logon process works for your target web site. For the purposes of this explanation, we will use the example of Mindmeister, a mind mapping app, as  our target web site. Please go to http://www.mindmeister.com and create an account. 


To get the information you need about the logon process that the target site uses, we’re going to use a Firefox browser add-in called HttpFox which tracks everything that happens during logon to a web site. You may use any equivalent application.

 

Follow these instructions:


- Run Firefox (http://www.mozilla.org/en-US/firefox/new)

- Install HttpFox add-in (https://addons.mozilla.org/En-us/firefox/addon/httpfox)

- Navigate to the logon page of the target website (http://www.mindmeister.com)

- In Firefox, under the ‘Tools’ menu, select Web Developer > HttpFox

- In the HttpFox window, press 'Start'

- Switch back to the target web site and logon with your credentials

- When you've logged on, switch to the HttpFox window and press 'Stop'

- Maximise the HttpFox window and switch to the 'POST Data' tab

- Go to the first event in the list and scroll down through the events until you see a POST event that contains your user credentials 

- Note the URL of this line, i.e. https://www.mindmeister.com/account/login

- Note the names of all parameters in the POST Data window, i.e. “login” for username and “password” for password. There may be more than two parameters so make a note of all of them and the value attributed to them in the ‘Value’ column. 

- Log out of the target web site.


You now have the parameters required to complete the configuration of the auto- logon tile. Enter them in the fields provided as below: 




NOTE: it is not possible to make an auto-logon tile for every website. Sometimes the logon configuration is designed to stop this process working as a security measure. Sometimes there are other anomalies that cause the process to fail. There may be some trial and error involved in getting an auto-logon tile to work. 


Widgets


Widgets are the functional component of FlightDecks. This is where you can view, configure and control settings in relation to individual widgets. 




Click the ‘Options’ button next to a widget to access the settings for that widget. The following settings are available: 


- This widget is available to everyone

- This widget is available only to selected roles

- This widget is not available for any role

- This widget is available at any location

- This widget is available only at the school location

- This widget is available except at the school location

- This widget not available at any location


Default launchpads


When you first log into Airhead, you have a default personal launchpad provided for you. As an Administrator you can decide which tiles to put on that default launchpad for each role type as long as permission to do so has been given to you. Each role type can have a different default launchpad. 




If you have permission, in the Administrator settings you’ll see a notice that says, “The default launchpad for this role is being inherited but you can override it.” If you click this button, you’ll then see an ‘Edit’ button appear and you can edit the default launchpad in exactly the same way you would add tiles to a personal launchpad. The launchpad graphic in the settings is a reflection of the actual default launchpad. 


When you’ve clicked the ‘Override’ button you will also see a new setting appear in addition to the ‘Edit’ button. This is a box that you can tick to allow the default  launchpad settings to be overridden by Administrators below your level. If you un-tick this setting, Administrators below your level will not be able to override your settings. 


Default launchpads are personal launchpads and therefore the user can change them. The purpose of a default launchpad is to give the user a starting point for using  LaunchPads. If you want to give a user a launchpad they cannot delete or edit, create a launchpad and share it with an individual user, role type or group of users. 


Default flightdecks


When you first log into Airhead, you have a default personal flightdeck provided for you. As an Administrator you can decide which widgets to put on that default  flightdeck for each role type as long as permission to do so has been given to you. Each role type can have a different default flightdeck.


 

If you have permission, in the Administrator settings you’ll see a notice that says, “The default launchpad for this role is being inherited but you can override it.” If you click this button, you’ll then see an ‘Edit’ button appear and you can edit the default flightdeck in exactly the same way you would add widgets to a personal flightdeck. 


When you’ve clicked the ‘Override’ button you will also see a new setting appear in addition to the ‘Edit’ button. This is a box that you can tick to allow the default launchpad settings to be overridden by Administrators below your level. If you un-tick this setting, Administrators below your level will not be able to override your settings. 


Default flightdecks are personal flightdecks and therefore the user can change them. The purpose of a default flightdeck is to give the user a starting point for using FlightDecks. If you want to give a user a flightdeck they cannot delete or edit, create  

a flightdeck and share it with an individual user, role type or group of users.