ClassLink Quick Start Guide
Give students and staff one place to open approved learning tools. Set up each app’s sign-in and roster access according to what the district approved.
This guide is for districts adding an application to an existing ClassLink environment. Available features and settings depend on the district and the provider.
What ClassLink Connects
Rostering
Roster Server takes data from the student information system (SIS) and shares approved school, user, class, and enrollment records with compatible apps using OneRoster.
Single Sign-On
LaunchPad opens supported apps using the sign-in method configured for each app. Test that the method reaches the right provider account.
Apps and Class Resources
District-assigned apps appear in LaunchPad. Where My Classes is enabled, instructors can make approved resources available in a specific class.
District Administrator Setup
Start with one approved application and a defined pilot group. Confirm with the provider which connections the app needs and which accounts, schools, and terms are covered.
Find the app and confirm its connection options
LaunchPad access
Find the provider’s app in the ClassLink Management Console (CMC). Check whether it is a web link or supports an SSO configuration such as ClassLink OneClick. Ask the provider which setup to use if several entries look similar.
Roster Server access
If the app needs rosters, find the provider’s Roster Server connection. Confirm which OneRoster version and delivery method the provider accepts, such as API or CSV, and who will confirm the initial load.
Set roster-sharing permissions
In Roster Server, configure permissions for the provider connection. Review the records the rules will include, compare them with the approved population, and confirm which data elements the vendor requires. If the district uses DataGuard, verify supported masking with the provider before rollout so account matching still works.
| Scope | What to verify |
|---|---|
| District-wide | The agreement covers the included schools and user roles. |
| Selected schools | The pilot schools are included and a school outside the pilot is excluded. |
| Rule-based cohort | The rules include the intended records and keep adjacent grades, classes, or roles out where applicable. |
Reconcile the roster before opening access
- SISConfirm IDs, schools, classes, and memberships.
- Roster ServerCheck the latest import and the app’s permitted records.
- Provider appConfirm receipt and compare representative classes and memberships.
Record the SIS import and provider refresh schedules. If counts disagree, compare the same schools, term, roles, and point in time. Trace a missing record through each handoff before adjusting the rules.
Assign the tile and finish account setup
Configure the app’s sign-in method and assign its LaunchPad tile to the approved pilot users through CMC. Confirm how the provider matches a signed-in user to a rostered account. If the app also needs LMS setup or directory account provisioning, coordinate those steps with the relevant owner. Where deployed, OneSync can manage the lifecycle of directory accounts.
Teacher Workflow
Use the district’s LaunchPad and the approved apps for your school or class.
Sign in and open the approved app
- Sign inUse the district’s ClassLink sign-in page and school account.
- Find the appLook for the assigned tile on LaunchPad.
- Open the appCheck that it opens under your school account.
Check your class inside the app
Open the expected school, section, and term in the provider app. Compare its student list with the district’s official roster. Report missing students, extra students, or duplicate classes using the district’s support channel before assigning work.
Organize resources in My Classes where enabled
Open My Classes from LaunchPad. Select the correct class, open Apps, and review what students can launch. If your district allows it, add approved resources from the App Library. A URL added here opens a website. SSO and roster delivery require their own configuration.
Test what students will do
Use a district-authorized test account or approved classroom check. Confirm that a student can sign in, find the tile or class app, and reach the correct account and class. If your school uses QuickCards, test the scan on the classroom device and handle cards as login credentials.
Configure, Verify, and Monitor
Configuration review
- LaunchPad assignments and roster permissions each match the approval.
- The provider confirms its required data and user-matching identifier.
- The SIS import and provider refresh schedules are documented.
End-to-end verification
- A pilot teacher and student find the app and reach the correct accounts.
- The provider displays the right classes and memberships.
- An out-of-scope test confirms the tile and roster records are excluded where intended.
| Symptom | First check | Next action |
|---|---|---|
| App tile is missing | LaunchPad app assignment and the user’s profile or group | Have the ClassLink administrator review the intended assignment in CMC. |
| Tile opens a sign-in error or the wrong account | Active school account, app sign-in settings, and provider identifier | Test with a district-authorized account and have the provider confirm its account mapping. |
| Students or classes are missing | SIS enrollment, latest Roster Server import, and app permissions | Trace one affected record through to the provider’s latest ingestion. |
| Students outside the pilot appear | Roster permissions and the provider’s prior or parallel imports | Confirm the source of the extra records, correct the scope, and coordinate removal with the provider under district procedures. |
| My Classes or a class app is missing | My Classes availability, instructor assignment, and class app access | Ask the district administrator to check the feature settings and verify the section in Roster Server. |
Practical Rollout Safeguards
Start with a pilot
Choose a few representative classes and devices. Expand once the district and provider confirm roster delivery, sign-in, and support handoffs.
Document decisions
Record the app owner, purpose, permitted users and data, sync schedule, test results, and support contacts. Use the district’s approved channel for student-level troubleshooting.