📘 FACTS / PowerSchool / Blackbaud integration (OneRoster)
FACTS, PowerSchool, and Blackbaud all speak a common standard called OneRoster 1.1. ThouShaltNotClick supports OneRoster directly, which means a single integration covers all three SISes (plus Aeries, Infinite Campus, ClassLink, and others that adopt the same standard). Auth is different from Google or Clever — you paste API credentials your SIS admin gives you instead of clicking through an OAuth redirect.
Before you start
- Your SIS needs OneRoster API enabled. This is usually a paid feature in your SIS — see the per-provider notes below.
- You’ll need three credentials from your SIS: Base URL, Client ID, Client Secret. Your SIS administrator generates them; we’ll show you exactly where in the per-provider sections below.
- No browser redirect required. Unlike Google Workspace or Clever, OneRoster uses OAuth client_credentials — you paste your credentials into TSNC’s form. We test them before saving.
FACTS / RenWeb specifics
Cost: FACTS charges schools roughly $500 / year for OneRoster API access. Your school’s FACTS account manager can confirm current pricing and add the API subscription to your plan.
- 1Open FACTS → System → Configuration → Integrations → OneRoster → API Export
Sign in to your FACTS admin portal (district code + admin credentials). Navigate to the OneRoster API Export form.
- 2Submit the form to FACTS Support
You’re requesting that FACTS issue your school API credentials. They’ll typically respond within 1-3 business days with the Client ID, Client Secret, and your school-specific Base URL.
- 3Check the “Faculty” checkbox
This is critical. By default, FACTS exports teachers as
administratorsvia the OneRoster API rather than asteachers. Without the Faculty checkbox, the “Teachers” mapping in TSNC won’t find anyone, and you’ll have to map “Administrators” → TSNC Teacher instead. Easier to just tick the box. - 4Come back to TSNC
Once you have your three credentials, open TSNC Admin → Integrations, click Connect SIS, pick FACTS from the provider dropdown, and paste:
- API Base URL — looks like
https://your-school.factsmgt.com/datahub/services/ims/oneroster/v1p1 - Client ID — usually a UUID
- Client Secret — a long random string. Treat like a password.
TSNC tests the credentials before saving. If anything is wrong (wrong URL, expired secret, etc), you’ll see a clear error message.
- API Base URL — looks like
PowerSchool specifics
PowerSchool’s OneRoster API is included with most PowerSchool tiers — no separate purchase needed in most deployments.
- 1PowerSchool → Data Plugin Setup → OneRoster connections
Your PowerSchool admin navigates to the OneRoster Connections panel. The exact menu path is sometimes under System Settings, depending on your PowerSchool version.
- 2Click Add new connection
Pick OAuth 2.0 as the auth method (NOT OAuth 1.0 — we don’t support 1.0). Set the connection name to “ThouShaltNotClick” or similar. PowerSchool generates a Client ID and Client Secret on save.
- 3Copy the URL, Client ID, Client Secret
PowerSchool displays the API base URL at the top of the connection details page. The Client ID is visible; the Client Secret is shown once at creation time — save it somewhere safe (1Password, etc).
- 4Paste into TSNC
In TSNC’s OneRoster connect form, pick PowerSchool from the dropdown and paste the three values.
Blackbaud specifics
Blackbaud’s OneRoster integration lives under Core → System tools → Integrations → OneRoster.
- 1Open Blackbaud Core
Sign in to your Blackbaud school management Core portal as a platform manager.
- 2System tools → Integrations → OneRoster → Add
Name the connection. Blackbaud generates a Client ID and Client Secret on save.
- 3Set scopes
Make sure the integration has access to users, teachers, and schools at minimum. Other scopes are optional.
- 4Paste into TSNC
In TSNC’s OneRoster connect form, pick Blackbaud Education Management from the dropdown and paste the three values.
Other OneRoster SISes
Aeries, Infinite Campus, ClassLink, Intellischool, and others also speak OneRoster 1.1. Pick Other OneRoster SIS in the provider dropdown — there’s no provider-specific validation, just the three standard credentials. Refer to your SIS vendor’s docs for where to generate them.
Mapping OneRoster roles
OneRoster 1.1 defines these standard roles:
- teacher — classroom teachers. Maps to TSNC Teacher.
- staff — non-teaching staff. Maps to TSNC Staff.
- administrator — admin staff (principals, IT, etc.). Maps to TSNC Staff or IT Admin (your choice).
- aide — teacher aides. Usually maps to TSNC Staff.
- proctor — exam proctors. Usually maps to TSNC Staff.
What syncs
- Email address (primary key for matching to TSNC users).
- First name, last name.
- OneRoster role + (optionally) school assignment.
- Active status (suspended users are deactivated).
What doesn’t sync
- Classes, sections, enrollments (we’re staff-focused).
- Students.
- Grades, attendance, behavior data.
- Parent / guardian info.
- Course catalog.
Common questions
I'm on FACTS and teachers are showing up as “administrators.”+
FACTS exports teachers as administrators by default. Go back to FACTS → System → Configuration → Integrations → OneRoster → API Export and check the Faculty checkbox. Save, then re-sync in TSNC. Alternatively, you can just map “Administrators” → TSNC Teacher in TSNC’s role-mapping editor — same end result.
How often should I sync?+
On demand. There’s no automatic scheduled sync yet (cron-style sync is on our roadmap). Click Sync Now after major staff changes — start of school year, new hires, mid-year departures.
Can I migrate from one SIS to another?+
Yes. Disconnect the current SIS (Disconnect button on the connection card), then connect the new one. Previously-imported staff stay in TSNC; the new SIS will update them in place rather than re-creating.
My SIS isn’t in the provider list. Will it work?+
If your SIS supports OneRoster 1.1, yes — pick Other OneRoster SIS from the dropdown. If you’re unsure whether your SIS supports it, ask your SIS support team for “OneRoster 1.1 API credentials.” If they say yes, you’re in business. If they say no or look confused, your SIS likely doesn’t support OneRoster yet.
What does the “test credentials before saving” step do?+
When you submit the connect form, TSNC immediately calls your SIS’s OAuth token endpoint with the credentials you provided. If the call fails (wrong URL, bad credentials, your SIS isn’t reachable), we surface the error and don’t save anything. You only get a successful save if your credentials definitely work.
How are credentials stored?+
The Client Secret is encrypted at rest with AES-256-GCM. The encryption key is held in our Railway environment, separate from the database itself. Even a full database leak doesn’t expose your raw secret. The Client ID is stored in plaintext (it’s shared widely in vendor docs and not considered secret on its own).