Student Portal - Google SSO Configuration

Overall Steps

1. Student Google email addresses imported.

2. Google SSO configuration enabled for Student Portal (By Illuminate Staff).

3. Student Portal accounts enabled via normal process through UI or via Import (details below).

Students can login by clicking a red ‘Sign in with Google’ button on the student portal, or you can link them to https://{district} and they will be automatically logged in.

Managing Google SSO for Student Portal

Please note, after enabling Google SSO, student passwords are no longer managed in Illuminate. You must enable the portal and align their Google Account in Illuminate. This means the following information must be true in order for Google SSO to work:

  • Google SSO is enabled.If this is not true, you must contact your Implementation Manager and follow the steps provided above.
  • In your Google Admin Console, your student must be assigned an email.You will need to speak internally with your district’s technology experts.  If Google Apps Configurations is enabled in Illuminate, you may assign students e-mails via Illuminate.  You may read more about this here.
  • In Illuminate, the students current email is set to their Google SSO email.You can do this in the Student Demographic Details Page. Click on their email address and you will be able to edit it.
  • Portal must be enabled for the student.This can be done under Students > Manage Portal Access.

You may enable portal by going to Students > Manage Student Portal.  If you need to add a student’s email, you do so on the Demographic Details page.  You must have the permission to Modify Student Demographics in order to do so.  You will click on the field and a editable text box will appear and allow you to update the field.

Otherwise, you may mass create them by re-importing your student_portal_accounts.txt file after updating it with new students, or by creating an automation.

Mass Enabling Portal Accounts

You can import or enable your student portal accounts using our Core Data Import Tools or through an Automation.  DnA Clients will want to create a script for this file.  Please note, this is the responsibility of the district to generate and push this file to our SFTP server.  

ISI clients will want to import it using the Core Data Import and Validation tool.

Please create a tab delimited file named ‘student_portal_accounts.txt’ with 5 columns.

  1. Student ID
  2. Username (Leave blank if not used)
  3. E-Mail (Leave blank if not used)
  4. Enable (1 for Yes, 0 for No)
  5. Temp Password (Leave blank when using LDAP / Google SSO)

How to Import: To import, go to the ‘Core Data Import / Validation’ tool within the Administration Menu.  You must add the “student_portal_accounts.txt” file to a .zip file before uploading via the interface. The filename of the .txt must match exactly ‘student_portal_accounts.txt’. See below for more information. If you are still unsure how to do this, please contact our help desk.

Automate: If you wish to automate importing this file, your district will need to create their own scripts or tools to pull the information from where the student_portal_accounts.txt data would be housed and pull it into the tab delimited file on the SFTP server on a nightly basis.  From there, please contact the help desk to update your Automation Profile Configurations to include the student_portal_accounts.txt file, if you are unsure how to do so.

To help get you started, you will likely need to contact your technology department to write a SQL query (or whichever database your Student Information System uses) and automate it nightly on your server/computer.  Most clients use Windows Scheduler to schedule a task.  You can find directions on how to set this up here:

Please note, the district / client is entirely responsible for automating the student_portal_accounts.txt file into the SFTP.  Illuminate currently does not have a courtesy tool or script.

Re-Import: Re-importing this file will update any email addresses or usernames.  However, temporary passwords will not be updated from re-importing the file.  You can force these to update by importing a file to disable the accounts by setting the enable column to ‘0’, then performing another import with ‘enable’ set to ‘1’.

How to import (for ISI Clients)

How to import (for ISI Clients)

1. Click the Admin Gear.

2. Click Core Data Import and Validation.

3. Enter your email address.

4. Upload the zipped file.

5. Select which schools this will be Viewable by.

6. Select the Config for your school.

7. Change the radio button to Run as Import.

8. Click Run Now if you want to import this now.

9. Waiting Time- If you run the import now, it will give the users a 10 minute warning that the entire site will go down to load the import.  The site will be unusable until the import has finished processing. You have the ability to change this if you like.

10. Select student_portal_accounts.

11. Click Upload.



Verify Integrity- Yes/No

Bypass Import Mode- Yes/No

Contact Data Import Mode- Replace/Add

Allow ISI data updates- Yes/No/Use Site Settings


Verify the upload

To verify and enable a student portal account:

1. Students - Manage Portal Access

2. Filter by student id in the search box at the top right of this page.

3. If the student does not appear, click on 'Add a Student'.

4. Find the student using the search interface.

5. Check the box next to their name and click 'Enable Portal' in the top right.

If the student cannot be found, double check that they have current enrollment and rostering.


  • Remember, after enabling Google SSO, passwords are managed by the District Administrator in charge of the Google SSO.  Please inform your users this and set this expectation.  
  • Enabling Google SSO will be a global change per Instance.  So, if Google SSO is enabled, all sites will see the button; however, until the username is switched to ther username@domain, they may continue to use the Illuminate log-in page.
    • If you need a special circumstance where an entire site/district in your district/consortium will be a case by case basis, please inform your Implementation Manager and they will contact a developer with specifics.