Brightspace supports the OneRoster v1.1 specification meaning it can integrate with many SIS implementations that also use OneRoster 1.1.
Synchronizing data with the SIS
Brightspace syncs data with your SIS during scheduled daily updates and manual admin-initiated syncs.
- Scheduled daily syncs and the Run Update Now button on the IPSIS Administration dasbboard retrieve all SIS changes since the last sync.
- The Resync Updates button on the IPSIS Administration dashboard enable admins to sync changes from a specified date.
- The Resync All SIS Records on the IPSIS Administration dashboard syncs all SIS data, typically limited to the current school year.
When a synchronization starts, Brightspace pulls rostering data in the following order:
- Academic sessions
- Orgs
- Courses
- Classes
- Users
- Enrollments
When the pull for daily syncs is complete, if you have enabled the grades export, Brightspace also sends grades data to the SIS.
Rostering assumptions and limitations
Allowable characters
Brightspace enforces character restrictions for Org Unit Codes and user fields:
- For Org Unit Codes, restricted characters are replaced with an underscore (_) by IPSIS to prevent errors, and codes are limited to 50 characters; longer codes are truncated.
- User fields have character limits and restrictions, but IPSIS does not replace illegal characters or truncate data.
For more information, refer to About Org Unit Editor or Create an individual user.
Deleting org units in Brightspace
Records for academic sessions, orgs, and courses with a status of tobedeleted are only deleted if all child org units are deleted first. In a standard SIS integration:
- A district can be removed once all child schools have been removed.
- A school can be removed once all child course templates and course offerings have been removed.
- A course template can be removed once child course offerings have been removed.
- An academic session (term) can be removed once child course offerings have been removed.
Enrollments in upper org unit
Users are enrolled into upper org units of type school when those org units are included in the OneRoster user record. Users who are enrolled manually in Brightspace cannot be unenrolled using the OneRoster integration.
|
Note: You can only use the OneRoster integration to unenroll enrollments from upper org units that were created after the June 2024/20.24.06 software update.
|
Exporting grades to your SIS
To export grades:
- The course must be created through the OneRoster SIS integration, with Grades Export enabled in the OneRoster SIS source system.
- The course can only be mapped to one active source system for grades
- Grades must be in categories retrieved from the SIS or enabled for export to the SIS.
- Grade items must have an Academic Session selected.
Categories
Categories are required to identify which grade items are exported to the SIS. Categories from the SIS have Export to SIS enabled by default. For integrations that cannot pull categories, teachers must enable Export to SIS manually.
For an SIS where Brightspace can create categories in the SIS, categories are synced if:
- The category has never been sent.
- The category was updated (name, deleted, restored) since the last sync.
- The category failed during the last export.
Grade Items
Grade items must have an associated academic session to export to the SIS. The Academic Session dropdown menu is visible when creating and editing a grade item. The menu is populated with all parents of the course offering that were created by the same SIS and where the SIS mapping in IPSIS Administration > Configuration is for the Academic Session of type term.
Grade items are synced if:
- They have never been sent.
- They were updated (such as name, academic session, points, deleted, restored) since the last sync.
- Their parent category was modified.
- They failed during the last export.
Brightspace uses the following logic to determine the OneRoster Assign Date:
- Use the Start date of the activity associated with the grade item.
- If no start date exists, use the activity Due Date.
- If no due date exists, use the activity End Date.
- If no end date exists, use the Academic Session End Date
Brightspace uses the following logic to determine the OneRoster Due Date:
- Use the Due Date of the activity associated with the grade item.
- If no due date exists, use the activity End Date.
- If no end date exists, use the Academic Session End Date
Student Grades
Student Grade are synced if:
- They have never been sent.
- They were updated since the last sync.
- Their parent grade item was modified since the last export
- They failed during the last export.