Integrations
Integrations, with honest status labels
We do not list a system as supported just because we could connect to it. Each row below says how the connection works, what it needs, and how far it has been tested.
Last reviewed: September 2026
What the status labels mean
| Label | Meaning |
|---|---|
| Validated | Running against a customer's production system. No integration has reached this level yet; this label will appear as they do. |
| Available | Built, in use, and supported. Used for file imports that do not depend on a vendor's API. |
| Beta | Built and working against simulated or documented behavior, but not yet confirmed against a live production system. Test it against your own test instance during evaluation. |
| Limited | Works with important restrictions, listed in the row. |
| Customer-specific | Built or adjusted for one institution's system as a paid add-on. |
| Roadmap | Planned, not built. No delivery date promised. |
| Not available | Not built and not currently planned. |
AtlasOA (higher education)
| System | Method | Direction | Needs from you | Data | Status | Limitations |
|---|---|---|---|---|---|---|
| Jenzabar J1 (Jenzabar One) | Read-only SQL over ODBC (SQL Server) | Read | SQL login with read-only rights (db_datareader); ODBC Driver 17 for SQL Server on the AtlasOA server | Terms, sections, courses, students, enrollments, instructors | Beta | Tested against a simulated database that verifies every statement is a SELECT; not yet run against a live J1 database. Encryption is on by default, but server certificate validation is off by default; turn it on if your SQL Server has a trusted certificate. |
| Jenzabar EX | Same SQL path, with schema detection | Read | Same as J1 | Same as J1 where EX uses J1 tables | Beta | Schemas vary by institution; confirm with a test database. |
| Jenzabar CX | REST API over HTTPS, OAuth2 client credentials | Read | API client ID and secret | Terms, courses, sections, enrollments, students, grades | Limited | Built from expected endpoint patterns without Jenzabar API documentation and not yet tested; needs adjustment against your CX API before use. |
| Canvas LMS | REST API over HTTPS, API token | Read | Canvas API token | Courses, sections, enrollments with grades, students, outcome results | Beta | No live campus connection yet; test against your Canvas test instance. |
| Blackboard Learn | REST API over HTTPS, OAuth2 | Read | Application key and secret registered by your Blackboard administrator | Terms, courses, memberships, users, gradebook | Beta | No live campus connection yet. |
| Moodle | Web services REST API over HTTPS | Read | Web service token created by your Moodle administrator | Courses, enrolled users, categories, groups, grade items | Beta | No live campus connection yet. Moodle passes the token in the request address; use HTTPS. |
| Jenzabar rubric report export (Excel) | File upload | Import | None | Students, sections, enrollments, rubric scores | Available | Specific report format. |
| Outcome assessment spreadsheets | Excel or ZIP upload | Import | None | Course outcomes and section achievement | Available | File naming convention required. |
| CSV templates | File upload | Import | None | Competency frameworks. Outcomes, assessment results, and closing-the-loop templates load into the evaluation sample workspace, and can be moved once into a new installation when converting to a trial. | Available | 2 MB or 10,000 rows per file. Ongoing score imports use the rubric report or outcome assessment spreadsheets. |
| AtlasOA REST API | JSON over HTTP(S), per-user bearer tokens | Read; competency framework writes by permission | A user token | Courses, outcomes, achievement, students | Available | No published OpenAPI specification yet. |
| Your SIS if not listed | Adapter built for your system | Read | Test access to your system | As agreed | Customer-specific | Paid add-on; see pricing. |
| Workday Student | Planned | Roadmap | ||||
| Banner, Colleague, PeopleSoft, D2L Brightspace, Google Classroom | None | Not available | Use CSV templates, or ask about a customer-specific adapter. |
Single sign-on (SAML, OIDC, LDAP) is not available for AtlasOA.
Atlas K-12
| System | Method | Direction | Needs from you | Data | Status | Limitations |
|---|---|---|---|---|---|---|
| PowerSchool | Vendor REST API, OAuth2 client credentials | Read | Plugin client ID and secret | Students, attendance, behavior, demographics, courses, grades | Beta | Not yet run against a live district system. |
| Skyward | Vendor REST API, OAuth2 or API key | Read | API credentials | Same as PowerSchool | Beta | Not yet run against a live district system. |
| Aeries | Vendor REST API, API key | Read | API key | Same as PowerSchool | Beta | Not yet run against a live district system. |
| Synergy (Edupoint) | Vendor REST API, API key | Read | API key (requires API entitlement from Edupoint) | Same as PowerSchool | Beta | Not yet run against a live district system. |
| Ed-Fi ODS / API | Ed-Fi API, OAuth2 | Read | Ed-Fi client key and secret | Students, attendance, behavior, demographics, courses, grades, assessments, calendar | Beta | Not yet run against a live district ODS. |
| OneRoster 1.1 (any compliant SIS) | OneRoster REST API, OAuth2 | Read | OneRoster client ID and secret | Students, demographics, courses, enrollments, grades | Beta | OneRoster does not carry attendance or behavior; supply those by CSV or SFTP. Enrollments are read but not yet imported, and date of birth is not populated correctly by this connector yet; supply date of birth by CSV. |
| Infinite Campus, Aspen, Focus, Genesis, eSchoolPlus, SchoolTool, Blackbaud, FACTS, Rediker, ProgressBook | Through the OneRoster connector | Read | Your vendor's OneRoster 1.1 API credentials | Same as OneRoster | Beta | Depends on your vendor's OneRoster API being enabled for your district. |
| CSV files | Upload or local folder | Import | None | Students, attendance, behavior, demographics, courses, assessments, calendar | Available | CSV only (not Excel). Sample files. |
| SFTP file drop | SFTP download from your server | Read | SFTP account; the SFTP server's host key must first be trusted on the Atlas K-12 server (for example by connecting once with ssh as the account that runs Atlas K-12). There is no screen for this yet. | Same as CSV | Available | Remote files are read, never renamed or deleted. |
| Tyler, Ascender, Alma, JMC, JCampus, WVEIS, Compass, SchoolBrains, others | CSV or SFTP (no public API) | Import | Scheduled export from your SIS | Same as CSV | Available | File-based only. API credentials are refused for these systems so none are stored unnecessarily. |
| Microsoft Entra ID | OpenID Connect single sign-on | Sign-in only | An app registration in your tenant | Staff identity | Beta | Single tenant. Off by default. Token validation is covered by automated tests; not yet confirmed against a district's production tenant. |
| Google Workspace sign-in | None | Not available | ||||
| Canvas, Schoology, Google Classroom, Moodle, Blackboard | Planned | Roadmap | ||||
| Screener presets (NWEA MAP, i-Ready, STAR, and others) | Planned CSV presets | Roadmap | Use the generic assessment CSV today. | |||
| Clever, ClassLink | None | Not available | ||||
| Public REST API | Planned | Roadmap |
Grade sync through the API connectors depends on section and enrollment data and is being confirmed as part of beta testing; CSV grade imports are the reliable path today. Detailed per-SIS setup and field mapping: SIS adapter matrix (PDF) and field mapping reference (PDF). Where a PDF differs from this page, this page is current.
Read-only data access: our approach
An integration should be able to read what it needs and nothing more. Both products are built so that a connection to your SIS or LMS can only read.
- No write-back. No AtlasOA or Atlas K-12 connector writes to your SIS or LMS. The only requests that send data to your system are the standard sign-in requests that obtain an access token.
- Read-only credentials. Give us an account that can only read. For Jenzabar J1 and EX, that is a SQL login with the
db_datareaderrole. AtlasOA sends only SELECT statements, and an automated test checks that no other statement type is sent, but the database login is your real safeguard. - Least privilege. Grant access only to the tables or API scopes the connector reads. For Jenzabar J1, AtlasOA reads
YEAR_TERM_TABLE,SECTION_MASTER,NAME_MASTER, andSTUDENT_CRS_HIST. - Test first. Connect to a test or non-production instance during evaluation, and compare the imported data with the source.
- Connection architecture. AtlasOA connects from the application server to the address you enter. Atlas K-12 connects only from its separate fetcher process, which may reach only the SIS hosts you configure for that job; the main application cannot connect out.
- Synchronization. Atlas K-12 syncs on the schedule you set (hourly, daily, or weekly) and recalculates tiers afterward. In Atlas K-12, only building and district administrators can create, change, or run connections.
- Credentials. Passwords and client secrets are encrypted at rest (Atlas K-12 in its database, AtlasOA in its local settings file); AtlasOA Canvas and Moodle API tokens are not yet encrypted. In Atlas K-12, leaving a secret field blank when editing keeps the stored value, so saved secrets are never displayed again.
- Logging. AtlasOA records every connection test in a local log (with the password removed) and in the audit log. Atlas K-12 records each sync in its sync history with a fixed error message; detailed errors go only to the server log. Atlas K-12's connection test currently shows administrators the raw error text from your system.
Do not take our word for it. Test it yourself. Install AtlasOA or Atlas K-12 on a machine your institution controls, use sample or non-production data, and let your own people decide.