Chromebook Onboarding - Part 1 - Google Cloud Platform

Adding Chromebook G Suite Domain to the Mobile Guardian school dashboard

In order to manage Chromebooks through the Mobile Guardian School Dashboard, one needs to authorize the Mobile Guardian school dashboard to see Users and Chromebooks Devices under your G Suite for Education domain. This allows the dashboard to pull in the list of users and devices registered under your Google domain.

Please note that this applies to both regular G Suite Enterprise as well as G Suite for Education Domains. It is required that your Chromebooks have been provisioned with a Chrome Device Management (CDM) license or what is know as Chrome Enterprise Upgrade or Chrome Education Upgrade. for more information about this please see the article in the link below:

https://support.google.com/chrome/a/answer/1289314?hl=en

Another thing to ensure is that you have turned on the Google Cloud Platform service in the G Suite admin. If you have not already done this please see steps in below.

https://support.google.com/a/answer/9197205?hl=en#:~:text=Google%20Cloud%20Platform-,Sign%20in%20to%20your%20Google%20Admin%20console.,Platform%20turned%20on%20or%20off.

Ready to get started

 Adding the respective JSON is a four-stage process requiring Super Administrator access to both your Google Cloud Console and G Suite Admin Console and finally uploading the JSON file into the Mobile Guardian school admin dashboard.

Part 1: The Google Cloud Console.

 Step-by-step guide

I. Login as a Super Admin user at https://console.cloud.google.com. This email address will also be referenced in the Mobile Guardian School dashboard.

II. Click on "Select Project"

III. Choose the relevant organisation from the drop down list and click "New Project" 

IV. Give your project a name that you will recognize in future and click "Create"

 V. Once the project has successfully been created you will see a confirmation of creation on the top right.

Before you continue to next step please ensure you are now switched to the newly created project.

VI. In the search field search for "Admin SDK" and select the API.

VII. You will then see the following screen. Click Enable.

VIII. Once you have clicked Enable, you will see the following screen.

IX. Click on "Credentials" on the LHS Nav then click on "Credentials in APIs & Services".

X. On the expanded credentials page click on "Create Credentials" and choose "Service account" from the drop down menu.

XI. You will now create a service account. Enter a service account name and click "Create".

XII. From the "Role" drop-down menu select "Project" > "Owner" then click "Continue"

XIII. Granting users access in this step is optional, therefore, at this step, you may click "Done"

XIV Once you have completed the service account you may now click on "Manage your credentials"

XV. You will be taken to the following screen where you must select the Elipses dot under actions and click on "Create Key" 

XVI. From the Pop up screen. Make sure JSON option is selected and Click "Create" to download the JSON file.

XVII. Once you have clicked on Create, a private key will be downloaded to your computer. Please keep this .JSON file as you will need it later to upload to your Mobile Guardian School dashboard. 

You may now proceed to click "CLOSE"

XVIII. Now you may select the actions three dots once more and click on "Edit" 

XIX. The next screen please click to expand "Show Domain-Wide Delegation"

XX. Enable G Suite Domain-Wide Delegation. This will enable you to manage all the Chromebooks in your domain. Don't forget to enter a Product name for the consent screen and click "Save".

XXI. Once you have successfully saved this information, you will be returned to the following screen with the status of your service account now enabled.

XXII. Now click on the top left (hamburger) menu to select API’s and services > Credentials

XXIII. Clicking on Credentials will show you the newly created OAuth 2.0 client ID. We will use this inside the G Suite Admin Console later

XXIV. Click the copy to clipboard icon as shown above to copy the Client ID.

Congratulations, you have now completed part 1 involving the developer console, now you are ready to move on to Part 2.

Back to the Top

We hope you found this useful.

Thanks for reading :)