BrighterBalance supports the IMS Global OneRoster 1.1 REST API for automated rostering of students, teachers, classes, and schools. Districts using ClassLink Roster Server or any other OneRoster 1.1 compliant rostering provider can integrate BrighterBalance without manual data entry. This article documents what data is rostered, supported authentication methods, and the setup process for district administrators.

Supported Standards

• OneRoster 1.1 REST API (IMS Global) — the OAuth 2.0 client credentials profile is supported for inbound roster pulls

OneRoster 1.2 is on the roadmap. Districts requiring 1.2 should contact us to discuss timing.

Compatible Rostering Providers

BrighterBalance integrates with any OneRoster 1.1 certified rostering provider, including:

A current list of OneRoster certified products is published by 1EdTech (formerly IMS Global) at https://site.imsglobal.org/certifications.

What Data Is Rostered

BrighterBalance pulls the following data from your rostering provider on a scheduled basis:

• Schools — name, identifier, district association
• Users — Teachers / Staff — first name, last name, email, school assignment, role
• Users — Students — first name, last name, grade, school assignment, student identifier (typically a state or district SIS ID)
• Classes / Sections — name, course, period, school, term, teacher of record
• Enrollments — which students are in which classes, and which teachers teach them

BrighterBalance only requests the minimum fields needed to operate the product. We do not request demographic data, IEP status, or special education classification through the OneRoster API.

Authentication

The OneRoster API integration uses OAuth 2.0 client credentials. During setup, your rostering provider issues BrighterBalance:

• A client ID
• A client secret
• The OneRoster API endpoint URL

These credentials are stored encrypted at rest in BrighterBalance's secure infrastructure and are used solely to pull roster data on the schedule configured for your district.

Single Sign-On (SSO) Options

Districts can pair the OneRoster roster sync with single sign-on so teachers and staff log in without a separate BrighterBalance password:

• ClassLink Launchpad — Add BrighterBalance from the ClassLink App Library and assign to staff
• Google Workspace OAuth — Native, requires no rostering provider
• Microsoft 365 Login — Native, requires no rostering provider

Setup Process

The full setup typically takes 1 to 2 weeks from kickoff to first sync. The general flow:

1. Discovery call (30 minutes). Your district IT team and the BrighterBalance team review your rostering provider, SSO requirements, and timeline.
2. Credential exchange. Your rostering provider issues OneRoster API credentials to BrighterBalance.
3. Initial sync and validation. BrighterBalance pulls a roster preview. Your district reviews the school list, teacher list, and student counts before going live.
4. SSO configuration. ClassLink, Google, or Microsoft SSO is configured and tested with a small group.
5. Production cutover. The roster is activated for the full district. Daily or hourly sync begins.

Sync Frequency

Default sync frequency is once per day, overnight. Districts can request more frequent syncs (every 4 hours, hourly, or near-real-time webhook for ClassLink) at no additional cost. Initial sync of a large district is typically completed within 30 minutes.

Data Privacy and Security

• BrighterBalance is FERPA compliant and adheres to the K-12 Student Privacy Pledge
• Student data is encrypted in transit (TLS 1.3) and at rest (AES-256)
• Student data is never sold, shared with advertisers, or used to train AI models
• The district retains full ownership of all rostered data and may request export or deletion at any time

A current Data Processing Agreement (DPA) and state-specific addenda are available on request.

Districts Without OneRoster

For districts that do not currently use a OneRoster 1.1 certified rostering provider, BrighterBalance is best deployed as individual or team subscriptions where teachers create their own accounts and add students manually. This path is well-suited to small pilots, single-school deployments, and individual-teacher subscriptions.

For full district-wide deployment under an Organization Plan, BrighterBalance requires a OneRoster 1.1 certified rostering provider. Districts evaluating BrighterBalance for an organization-wide rollout without a current rostering provider should contact us — we can discuss options including pilot programs that run in parallel with a rostering provider procurement.

Setup Contact

To start a rostering integration, email hello@brighterbalance.app with:

• District name and state
• Approximate number of teachers and students
• Rostering provider in use (ClassLink, Infinite Campus, PowerSchool, Skyward, etc.)
• Preferred SSO method
• Target launch date

We'll follow up to schedule a setup call.