Login to Aeries

Login to Aeries as an Administrator and navigate to the Google Apps Integration form (School Info | Configurations | Google Apps Integration).  Please note that while the navigation is currently under School Info, these settings are in fact for the district and need only be set once.  You will see five tabs:

  • Directory Sync Settings - pertain to how you want your student accounts formatted and how you want Aeries to interact with Google for directory synchronization.
  • Google Classroom – configuration options for Google Classroom.
  • Organizational Unit Structure - describes how your students will be organized inside of Google. This tab is only applicable to directory sync.
  • Google Service Account Settings - should only need to be configured once and then can be left alone.
  • Maintenance Functions – contains several functions for maintaining the Google integration

Note: Directory Sync is recommended but is not necessarily required to be used to integrate with Google Classroom.


The Google Service Account Settings should be configured first.


Google Service Account Settings

This is where you will copy information from the Google Developers Console (https://console.developers.google.com)

  • API Application Name – This is the project name you entered in an earlier step (e.g., "Aeries Integration")
  • User to Impersonate – This is the Aeries Service account you created in an earlier step (e.g., "AeriesService@yourdomain.org")
  • Student Domain – This is the domain (NOT the organizational unit) your students will belong to and will serve as part of their Google account’s address (i.e., everything after the “@” symbol in the student's Google account)
  • Teacher Domain – This is the domain (NOT the organization unit) your teachers belong to. This may or may not be the same as the Student Domain depending on your Google configuration. Some districts like to separate their students and employees into separate domains.  This is the place to tell Aeries that domain.
  • Service Account Client ID – This is the Client ID that belongs to the Service Account and should be visible in the open Developers Console tab (from an earlier step)
  • Service Account Email Address - This is the email address that was generated when you created the Service Account and should be visible in the open Developers Console tab (from an earlier step)
  • P12 Private Key File Name – This is very important.  This is the name of the file - including the .p12 extension - you downloaded in an earlier step.  It should be placed in your AppSettings folder of your web server and the AeriesReporting\Service folder of your Aeries Reporting Server.


Directory Sync Settings

  • Synchronize all students nightly – This will add accounts for students who do not currently have a Google account associated with their Aeries account, or suspend accounts which are associated, but are no longer active in Aeries.
  • Show Google Account options on Student Demographics Page - This will add a button near the Student Email field on the Student Demographics page. Only users with update permissions to the External Student IDs table will see the button. Users will be able to manually link and un-link students with existing Google accounts. (See below for details). Note: this option will be ON by default.
  • Automatically sync student accounts when added via Aeries SIS Web - This will asynchronously sync the new student to your Google domain whenever a student is added via Aeries SIS Web Version.
  • Override Existing Student Emails (STU.SEM) with Pattern – Determines if the nightly process should override any existing values in the student email field that do not match the pattern and replace those values with the student’s current or newly create Google account.
  • Student Root Org Unit – The top level Organizational Unit students will be added to.  This is critical as you can act on all student accounts from within the Google Admin Console by nesting them under one org unit.
  • Student User Name Pattern - This is the pattern that will be applied to all student accounts in Google. Possible elements are [first-name], [last-name], [permanent-id] etc. These pattern elements can be modified with LEFT and RIGHT string functions to allow you to form a custom string with whole data or parts of each data element to build the pattern your students will have for their accounts.

    It is not recommended to change this pattern once you have begun synchronizing students to Google.

    Examples for student John Smith, #1234, DOB: 1/2/2001, grad year 2019


    [first-name][last-name][class-of]
    johnsmith2019
    [last-name]RIGHT(2,[birth-year])
    smith01
    First letter of first name, first 4 letters of last name, last 3 of student ID
    LEFT(1,[first-name])LEFT(4,[last-name])RIGHT(3,[permanent-id])
    jsmit234


  • Student Password Pattern – Like the student user name pattern, but just for the password. Use a pattern that will ensure all passwords will be at least 8 characters long.
  • Force New Students to Change Password on First Login to Google Apps – Newly created students will be forced to change their password.
  • Match New Student PWA Passwords (Student Portal) to Password Pattern - Any newly added students that have PWA accounts (Student Portal) will have that password match their Google account password.
  • Suspend Accounts for inactive students - When this option is turned on, students who become inactive in Aeries will have their Google accounts suspended. This option is on by default.
  • Manage the Location of Existing Student Accounts in the Google OU structure - When this option is turned on, existing students will be moved from one org unit to another in Google based on information in Aeries (e.g., school code or grade level) and the chosen org unit structure. This option is on by default.
  • Suspend accounts that are no longer linked to a student record – This option will suspend any Google account nested under the student root org unit that was previously linked to a student in Aeries but for which there is currently no Student Data (STU) record in Aeries.
  • Suspend accounts outside the age/grade ranges -  This option will suspend any Google account nested under the student root org unit if the student in Aeries is outside a specified grade range and/or age range
  • Sync students in grades – Only students in the specified grade range will be synced to Google.
  • Sync students who are between these ages – Only students in the specified age range will be synced to Google.
  • Schools to Synchronize – The set of schools that will be included in the directory sync process.


Google Account Options on Student Demographics Page

When the option to Show Google Account options on Student Demographics Page is turned on, users with update permission to External Student IDs will see a button with the Google icon next to the Student Email field.



Click the button to display Google Account Options for this student. This feature allows districts to correct the Google account to which a student ID is linked in case an incorrect link was initially made. This situation can occur when Aeries is integrated with a G Suite for Education domain that is already up and running, and the Student Email in Aeries does not match the existing Google Account, or in scenarios where a username pattern is selected that leaves room for ambiguity (such as students with the same name).



The current Student Email (STU.SEM) will display in the text box. Changing this value will NOT update STU.SEM; it will only update the Google account to which this student is linked. Click the Link button to link this student ID to the selected Google account. If the student was previously linked to a different Google account, that link will be removed.


If the student is already linked to a Google account, that account will display next to the Un-Link button. Click the Un-Link button to remove the link between this student ID and the Google account.


Connection Confirmation

You have now entered all the data elements necessary to connect to Google.  Click the Save button at the top or bottom of the page, and the Configuration Status message should display a green check mark next to Google Directory Sync. If not, it will tell you what the error message is from Google and be red. If you completed the steps to connect to Google Classroom, there should be a second green check mark. Otherwise, there will be an error message in red.



Google Classroom

Enabling Google Classroom will allow your teachers to import assignment scores from Google directly to their gradebook (Scores by Assignment page). It will also allow them to create a Google Classroom class with students already joined, or to link to an existing Google Classroom class from the Class Summary widget on the Teacher Portal home page. This feature is available for all school types. For schools with a Master Schedule, teachers link Google Classroom classes to the sections in the Master Schedule. For elementary schools with no Master Schedule, teachers link Google Classroom classes to their Aeries Gradebooks.

  • Synchronize all classrooms nightly - This will populate existing Google Classroom classes with the current roster of students during a nightly process.
  • Automatically add students to Google Classroom when scheduled in Aeries - This will asynchronously add new students into Google Classroom classes whenever they are scheduled into a section or Gradebook in Aeries that has been linked to a Google Classroom class.
  • Improve Performance – This should only be checked if your District is using Directory Sync or if you regularly run the Populate External Student IDs function from the Maintenance Functions tab. With this option on, Aeries will rely on the External Student IDs (ESI) table to identify students’ Google accounts and will not search the Google domain to find student accounts. This results in fewer Google API calls and faster performance of the Google Classroom integration.
  • Schools to Enable Google Classroom – The set of schools for which Google Classroom integration is enabled. Only teachers in the selected schools will be able to use any of the Google Classroom features within Aeries, including the import to Gradebook.

Note: Aeries will not remove students from a Google Classroom class if they are dropped from the class in Aeries. Aeries will only add students. This way no student work or submitted grades are lost in case the student is removed erroneously or if the student returns to the same class at a later date.


First, review/enable permissions for your teachers to use Google Classroom. Follow this link to learn how to set up those permissions https://support.google.com/edu/classroom/answer/6071551?hl=en.

Next, make sure that teachers who want to use Google Classroom have their Google email address stored in Aeries. They will then be able to create new Google Classroom classes or link to existing ones, and automatically join their students to those classes directly from the Class Summary within Aeries.  Teachers can also import scores from Google Classroom into the Aeries Gradebook.


IMPORTANT NOTE: For students to be added automatically when a Google Classroom class is created, the students must also have valid Google accounts known to Aeries, whether stored in the ESI table or in the student email address field (STU.SEM).


Staff must have their Google email address populated in the Email Address field (UGN.EM), or the Google Account field (SSO.GEM). This is set on the Security Users form.



Aeries will try to use the regular Email Address to locate their Google account. If their Google account is different from their regular email address, then the Google Account field must be populated with the Google account name.


If your District is not using Directory Sync options, but wishes to use Google Classroom for your teachers, STU.SEM must be populated with the student’s Google email address.

 

Organization Unit Structure

This section is where you will decide the nested structure for your Organization Units in Google. The process that copies your desired structure to Google will only add Org Units. It will never delete them. If you decide on a structure, and then decide to change it in the future, you must manually remove any unused org units from the Admin Console. Students will be added to whatever the current directory structure is.