Installing the Blocksi Enterprise Edition Extension

Created by Customer Support #1, Modified on Tue, 09 Apr 2024 at 04:07 AM by Customer Support #1

The Blocksi Enterprise Edition (BEE) extension is available on the G Suite Marketplace and Chrome Webstore. You install it on the Google Admin console.

Installing the Blocksi BEE is broken into three parts:

  • Part 1: Adding the Extension to Your Google Console

  • Part 2: Setting Up the Chrome Restrictions

  • Part 3: Setting Up the Device Restrictions

Part 1: Adding the Extension to Your Google Console

To add the extension to your Google console

  1. Sign in to the Google Admin console using your Google Admin or Microsoft credentials.

  2. Click Devices.

    Google Admin Console Main Screen

  3. Click Chrome devices.

    Google Admin Console Chrome Devices Screen

  4. Click Apps & extensions from the Main Menu to the left.

    Google Admin Console Select Apps & Extensions

  5. Click Users & browsers. The Users & browsers tab opens.

    Google Admin Console Select Users & Browsers

  6. Select and highlight the organizational unit (OU) where the users to be filtered are located, or if the school district intends to filter the entire domain, then you need to highlight the root domain.

    Google Admin Console Select OU

  7. Hover your mouse cursor over the Add Icon icon located in the lower right-hand corner of the screen and click the Waffle Icon icon. The Add Chrome app or extension by ID window opens.

    Google Admin Console Add Chrome App or Extension by ID Window

  8. Sign in to the Blocksi Admin Dashboard using your Google Admin or Microsoft credentials.

  9. Click the Copy Blocksi Enterprise ID button in the Action Bar of the Admin Dashboard. This copies the Blocksi Enterprise ID to the clipboard.

    Copy Blocksi Enterprise ID Button

  10. Return to the Google Admin console and paste the ID into the Extension ID text box.

    Google Admin Console Add Chrome App or Extension by ID Window

  11. Click Save. The Google Admin console now displays the BEE. By default, the extension is set to Allow install under its Installation policy settings.

    Google Admin Console Allow Install

  12. Click the down arrow to the right of the Allow Install option and switch it to Force Install.

    Google Admin Console Force Install

  13. Click SAVE in the upper right corner of the console to save your selection.

Part 2: Setting Up the Chrome Restrictions

To set up the Chrome restrictions

  1. Click Settings from the Chrome menu.

    Google Admin Console Select Settings

  2. Click Users & browsers. The Users & browsers tab opens.

    Google Admin Console Select Users & Browsers

  3. Click the OU with which you plan to monitor students with the Teacher Dashboard. The selection shown here is for example only; yours may be different.

    Google Admin Console Select Teacher OU

  4. Type screenshot in the + Search or add a filter field and press Enter.

  5. Click the down arrow to the right of the Screenshots option and ensure it is set to Allow users to take screenshots and video recordings. If it is not, then switch it. This enables the capture of screenshots and video recordings of student devices by teachers for monitoring and assessment purposes.

  6. Type screen video capture in the + Search or add a filter field and press Enter.

  7. Click the down arrow to the right of the Screen video capture option and ensure it is set to Allow sites to prompt users to share a video stream of their screen. If it is not, then switch it. Enabling this setting allows teachers and students to share their screens to the Teacher Dashboard or student devices, enhancing collaboration and instructional capabilities.

  8. Click SAVE in the upper right corner of the console to save your selections for this OU

  9. Click the Students OU. You need to prevent students from accessing task manager, incognito mode, and developer tools. The selection shown here is for example only; yours may be different.

    Google Admin Console Select Students OU

  10. Type task manager in the + Search or add a filter field and press Enter.

  11. Click the down arrow to the right of the Task manager option and switch it to Block users from ending processes with the Chrome task manager. Enabling this setting prevents students from ending the Blocksi extension process through the Chrome Task Manager and gaining temporary unrestricted access.

  12. Type incognito mode in the + Search or add a filter field and press Enter.

  13. Click the down arrow to the right of the Incognito mode option and switch it to Disallow incognito mode. Disallowing Incognito Mode prevents students from disabling extensions, including Blocksi. This ensures that Blocksi can continue to effectively monitor, manage, and filter student activities.

  14. Type developer tools in the + Search or add a filter field and press Enter.

  15. Click the down arrow to the right of the Developer Tools option and switch it to Never allow use of built-in developer tools. By disabling Developer Tools, students are unable to access Chrome Shell (CROSH), a command line interface that offers similar functionality to Linux Bourne Again Shell (BASH) or Windows command terminals. Because CROSH mode grants full access to the Chromebook, restricting this access is vital to upholding the security and effectiveness of the filtering system.

  16. Click SAVE in the upper right corner of the console to save your selections for this OU.

Part 3: Setting Up the Device Restrictions

To set up the device restrictions

  1. Click Device from the Settings menu.

    Google Admin Console Select Devices

  2. Select the OU in which your schools have their devices enrolled. You need to prevent students from being able to sign in using guest or to other domains.

  3. Type guest mode in the + Search or add a filter field and press Enter.

  4. Click the down arrow to the right of the Guest mode option and switch it to Disable guest mode. Disabling guest mode prevents students from accessing unmanaged sessions on Chromebooks, ensuring that the necessary extensions, including Blocksi, are pushed to their devices.

  5. Type sign-in restriction in the + Search or add a filter field and press Enter.

  6. Click the down arrow to the right of the sign-in restriction option and switch it to Restrict sign-in to a list of users. By allowing specific domains, this setting restricts sign-in to only authorized users, enhancing security and control over Chromebook devices.

  7. Type your domain in the Allowed users field that appears. Remember to include *@ in front of the domain name.

  8. Type autocomplete domain in the + Search or add a filter field and press Enter.

  9. Click the down arrow to the right of the Autocomplete domain option and switch it to Use the domain name, set below, for autocomplete at sign-in.

  10. Type your domain in the username@ field that appears. Entering your domain allows the Chrome browser to prefill the domain for users, simplifying the sign-in process and enhancing user experience.

  11. Type Chrome management for signed-in users in the + Search or add a filter field and press Enter.

  12. Click the down arrow to the right of the Chrome management for signed-in users option and set it to one of the following, depending on your district's requirements:

    • Apply all user policies when users sign into Chrome, and provide a managed Chrome experience: Selecting this setting pushes all extensions deployed to the user's account when they are on a personal device.

    • Do not apply any policies when users sign into Chrome. Allow users access to use Chrome as an unmanaged user: Selecting this setting removes any extensions deployed to the user's account when they are on a personal device.

  13. Click SAVE in the upper right corner of the console to save your selections for this OU.

  14. Repeat Parts 2 and 3 for each student organization in your district.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article