The Settings section of Relay allows you to set a variety of Relay settings and manage your Google users and Chrome extension.
You can access Settings by navigating to Settings in the main left-hand Relay navigation menu and then selecting one of the Settings sections.
The Blocking section of Relay allows you to set your Block Screen and add users with Override privileges.
You can access the Blocking section by navigating to Settings > Blocking in the main left-hand Relay navigation menu.
The Block Screen section of Blocking allows you to set the block screen that a user will see upon attempting to visit a blocked site. All users who attempt to access blocked sites will see the block screen. Users with Override privileges will be able to override the category blocking the content for two hours in order to obtain access. Overrides will be covered later in this section. Navigate to Block Screen and click Edit to edit your Block Screen.
On the Edit page, you will be able to customize your Block Screen. Utilize the left-hand navigation menu to customize a variety of options, including Accent Color, School or District Name, Body Text, and Footer Text. Click Save to save your changes, or Cancel to discard your changes. The following is the default Block Screen prior to customization.
The following is a customized Block Screen for our Test District.
Users with Override privileges can override the category blocking the content for a set duration if they wish to access any blocked content. These users will be able to click an Override image on the Block Screen to override the block. Overrides only work for categories that allow Overrides (Internet Access >Rules)
You can add an Override by navigating to Overrides and clicking the green “+” sign to the right.
The following box will pop up. Here you can search for any user within the Search box. Once you have identified the user, check the box to the left of their name and click Save.
You will then see the user added to the Overrides list. You can delete any users’ override privileges by clicking the gray “x” to the right of their username. You can enable or disable Overrides for your entire staff by toggling the All Staff switch on () or off ().
You can determine if a category can be overridden or not by navigating to Internet Access > Rules > Categories. Here you can check the Override box next to any category in order to allow users to override it.
The Chrome Extensions section provides instructions for deploying the Chrome Extension and setting up optional (but recommended) Google Admin Console settings. Deploying the Chrome Extension is the first step to setting up Relay and should be completed upon getting started. You can access the Chrome Extensions instructions by navigating to Settings > Chrome Extensions. You can also find detailed instructions here.
In addition, optional extensions are available for tracking user and device locations.
Tracker collects a user’s location history from any device they are signed into and displays it in the Users section of Relay.
Device Detective helps recover lost or stolen devices. It runs as a full-screen kiosk app displaying a custom message, collects device location data, and shares it in Relay’s Device Detective section.
The Flagged Terms section allows you to set up flagged terms and email notifications. Setting up flagged terms and email notifications is the third step of Relay setup. You can access the Flagged Terms section by navigating to Settings > Flagged Terms.
Flagged terms come in three levels: low, moderate, and high. The higher the level, the higher the danger level of the term. We came up with some flagged terms for our testing environment. As you can see, we’ve classified highly worrisome and offensive terms (ex. xxx, suicide, make bomb) as High. We classified a few more general terms (ex. sex, marijuana) as Moderate and a few terms that could potentially be innocent, but could also potentially be offensive or worrisome (ex. pot, hate, nude) as Low.
Email notifications are key to monitoring your network and ensuring student safety. Email notifications notify you of users who search for flagged terms. You can assign any term to be flagged. These are usually unsafe, pornographic, or violent terms, as well as any other term that students should not be searching for, or a term that would raise concern if students were searching for it (ex. “suicide”.)
Before you set up email notifications, you need to create flagged terms.
To individually add a flagged term, click the green plus sign to the right of the search box.
Enter your desired term and choose the level of severity. In the example, we entered murder as the term and chose a Low severity from the dropdown menu (we want the term to be flagged, since it could potentially be worrisome, but we also understand that a student could be searching for “murder” as part of a History or English class assignment.) Click Save.
You will now see the term added to the list of terms. You can search for a term within the list by using the search box. You can delete any term from the list by clicking the gray “x” to the right of the term.
In addition, you have the option to upload a list of flagged terms developed by Lightspeed Systems. You can download the CSV from here. Once you have downloaded the list, click the import icon to the right of Terms.
Click on Choose File, navigate to the directory where the badterms.csv file downloaded, select the file, and click Import.
Similarly, you can develop your own .CSV file and upload it. Each CSV file should have a basic formatting of “term, number”. The numbers range from 1 to 3, 1=Low, 2=Medium, 3=High.
Once the terms have been imported, you will see a long list with various danger levels under the Terms header. You can sort the list by importance and make any adjustments by editing or deleting any term.
Once you have added your flagged terms, you can set up the type and frequency of email notifications detailing flagged terms being used by students. To set up an email notification, scroll to the top of the Flagged Terms page and click the green plus sign to the right of Email Notifications.
Next, select the administrator that you want to send email notifications to by clicking the green plus sign to the right of their email address.
Note: When adding users, a badge differentiates school admins from district admins.
On the Notification Preferences box, select the Danger Level of which you want the administrator to be notified. Selecting a Danger Level of 1 will notify the administrator of every single instance of a user searching for a flagged term, no matter the severity. Selecting a Danger Level of 5 will only notify the administrator of extensive use of flagged terms by a user. You will also need to select the Frequency of notifications (Immediately, Daily, or Weekly.) In our example, we selected every single Danger Level and immediate Frequency to instantly receive reports of all flagged term searches. You will need to determine the ideal settings for your organization. Click Save to save the email notification. Repeat this process for all other administrators that you want receiving email notifications.
The administrator’s email, Danger Level, and Frequency will now show under Email Notifications. You can edit a notification by clicking the mail address or delete a notification by clicking the gray “x” to the right of the notification.
The Device Detective section allows you to enable Device Detective for tracking lost devices, provides instructions for adding the corresponding Chrome extension to devices, and setting a custom recovery message. You can access Device Detective Settings by navigating to Settings > Device Detective.
Important: Before enabling this feature, we recommend that schools obtain appropriate parental consent for its use with student Chromebooks when needed.
You can enable or disable Device Detective by toggling the Enable switch.
You can set a custom Recovery Message in the field under the Recovery Message section. This message will display on devices after they have been reported lost or stolen.
The User Management section allows you to sync Relay with Google Admin. This will import your organizational units or users from Google Admin console. You may want to complete this step if your organization uses email addresses that do not clearly define who the user is (ex. student IDs as e-mail addresses.) Importing your organizational units and users into Relay will clearly define who your users are in your reports. You can access the User Management section by navigating to Settings > User Management.
Under Google Import click Authorize.
You will be redirected to a Google page that will prompt you for permission to allow Lightspeed Systems to view organizational units on your domain. Click Allow.
You will now see new options under Google Import. Here, under the Data tab you will have to choose whether you want to import Structure Only (the structure of your organization – groups) or Structure & Users (the structure of your organization as well as your users.) Under the Organizations tab make sure to select the correct organizations to import. Click Import to finish the process. (The example below shows organizational units for our sample district. Your options will look different and will be based on your district/schools.)
Once you click Import, you will receive a notification that importing is in progress.
After importing, you can enable nightly sync with Google by checking the Nightly Import box. You can also always perform a manual import by clicking Import Now.
Once your structure and/or users are imported, you will be able to see them by clicking the switch groups button to the right of Home on the Relay Dashboard.
Navigate to the school or schools you imported, and you will be able to see the structure within each school.
You will also have the option to organize your users and groups granularly through Launch Admin Tools. You can learn more about importing users via Launch here.
Note: API Access needs to be enabled in order for Google sync to work.
Within Google Admin, navigate to Security > API Reference and check the Enable API Access box under API access.