Classroom Crextnaut Migration Instructions

Overview

Here is a quick video detailing the process from start to finish. 

 

Migrating from an existing Chrome extension requires the following general steps.

  1. Find your installation URL
  2. Remove the old extension policy
  3. Add a new extension policy
  4. Configure the update URL

 

Find Your Installation URL

This url can be constructed by finding your school’s orgID. This identifier can be found in the URL bar after logging in and will look like “org1234”

Once you have your orgID, your installation URL will look like this:

SAMPLE https://crextnaut.securly.com/subscribers/ YOUR ORGID /update-manifest.xml SAMPLE

 

 

Remove the old extension policy

To avoid any conflicts or confusion, you will want to ensure that you have removed extension policies that previously were installing the Securly Classroom extension.

Old Extension ID: jfbecfmiegcjddenjhlbhlikcbfmnafd

DO NOT Remove any other extensions. This is for Securly Classroom only. 

 

Add a New Extension Policy

Each extension type has a new Extension ID to ensure a successful transition.
New Extension ID: hkobaiihndnbfhbkmjjfbdimfbdcppdh

 

Google Workspace

  1. In Google Workspace, navigate to Devices > Chrome > Apps and extensions > Users & browsers
  2. Select the OU you want to deploy the extension to and click the "+" button in the bottom right and select "Add Chrome app or extension by ID
  3. Paste in your extension ID and change the dropdown to “From a custom URL”
  4. Paste in your Installation URL.

  5. The installation policy for our extension should be set to "Force install" or Force install + pin" (this will allow you to see the extension in your browser's toolbar.
  6. Set "Permissions and URL Access" to "Allow all permissions
  7. Click on "Save" in the top right corner.
  8. Important - Configure the update URL: Scroll down in the right-hand pane. At the bottom, in "Deployment settings > Update URL", select “Installation URL”.

 

Configure the Update URL 

It is important to note that each of the above sets of instructions included one more step than is typically required of Securly extensions. This final step in each case is to configure the Update URL to point to match the Installation URL. Failing to do so will result in losing flexibility in the ways bug fixes and features can be targeted to your district as well as lead to less predictability on rollout schedules for your school.

Was this article helpful?
12 out of 12 found this helpful
Have more questions?
Submit a request

Comments

0 comments

Please sign in to leave a comment.

Articles in this section