Prerequisites in Skolon

To install Skolons Lifecycle Management for Google, you will need the following in Skolon:

• Users, classes and groups in the Skolon Platform

• Email addresses in Skolon, either synced from your MIS or generated in Skolon.

  • Read more about email generation in Skolon in this article Email generation in Skolon

• A valid agreement with Skolon that covers the use of the Skolon Google LCM

Prerequisites in Google Workspace

You will need a Google Workspace for Education domain with a super admin account. The integration requires:

1. A Google Cloud Project Service Account with an associated JSON private key.

2. Domain-Wide Delegation authorizing the service account to impersonate a Workspace administrator.

The impersonated user must be a superAdmin for the sync to function correctly.

The following Directory API OAuth scopes needs to be added:

https://www.googleapis.com/auth/admin.directory.group
https://www.googleapis.com/auth/admin.directory.orgunit
https://www.googleapis.com/auth/admin.directory.user
https://www.googleapis.com/auth/admin.directory.user.alias
https://www.googleapis.com/auth/admin.directory.userschema

If Google Classroom course sync is enabled, the following Classroom scopes are also required:

https://www.googleapis.com/auth/classroom.courses
https://www.googleapis.com/auth/classroom.profile.emails
https://www.googleapis.com/auth/classroom.profile.photos
https://www.googleapis.com/auth/classroom.rosters

Google Connection Credentials

You will need a Google Workspace for Education domain with a super admin account. The integration requires:

Skolon connects to your Google domain by using the Google Workspace API:s. To install the integration you need to create service account credentials in Google and share them with your Skolon representative. Skolon needs the following:

• A JSON key (credentials.json) generated as instructed in the following support article written by Google

• The email adress to the service account created in your Google environment

Organizational Units

Skolon generates and maintains organizational unit (OU) structures in the Google Admin Console. For each school, Skolon creates an OU for staff and separate OUs for each student class, ensuring that policies and settings can be applied correctly per role or group.

On installation, Skolon will generate a new OU structure inside your Google domain. It is possible to run the integration to generate OUs without moving users as a first step. Note that the sync is non-destructive for the directory structure: it can create OUs and move users, but it will not delete an OU even if it becomes empty.

Dry run validation

Before the first live sync, a Skolon representative will run the integration in dry run mode. This produces a set of delta files (delta_org_units.json, delta_schools.json, delta_deleted_users.json) that list every change the sync would make in Google. Review these files together with your Skolon representative and confirm the result before any change is applied to your production Google environment. Scheduled syncs always run live—dry run is only for validation.