Project Atlas AetherDev project hub
Atlas project production

Aeries to Clever Rostering and SSO Hub

Publish Aeries roster and identity data into Clever as the central hub for instructional access, SSO, downstream application provisioning, and app-assignment governance.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-26
Visibility
Internal

Purpose

Document Clever as the district's central instructional access and rostering hub rather than leaving it buried in a broader ecosystem note.

Current state

The registry now treats Clever as a first-class parent governance hub, not just a sync endpoint. Production evidence includes an enabled Integr8r Clever job, historical weekly-report references to nightly Aeries-based access updates, and a current Clever inventory snapshot. Operationally, Clever is both distribution runtime and policy surface for app enablement and district data sharing.

Next step

Document the current scheduler, export contract, app-assignment change-control process, and the boundary between first-class child integrations and inventory-only Clever apps.

Interfaces

Inputs
  • Aeries student, teacher, course, section, class, school, and enrollment data
Outputs
  • Clever roster and identity state
  • downstream application access and SSO readiness

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

  • Aeries is canonical for roster and identity source data published to Clever.
  • Integr8r Clever job configuration plus Clever tenant app-assignment settings define the active operational contract.
  • Clever is the distribution hub and governance layer for connected application access, not the authoring source for SIS records.

Safe handling

  • Treat Clever-connected app assignment and roster state as restricted instructional data.
  • Document app governance and vendor-sharing decisions internally.
  • Review downstream app access whenever roster or SIS field logic changes.

Operational notes

Reliability posture

This is now one of the highest-impact district integration hubs. Failures create broad classroom access issues across multiple downstream apps.

Observability

  • Integr8r runtime and diff behavior
  • Clever admin validation
  • site-level access incidents when provisioning drifts

Security and privacy

Clever distributes restricted student and staff instructional data to multiple vendors. App assignment governance and roster accuracy are key privacy controls.

Dependencies

Upstream
  • Aeries data quality
  • Clever configuration health
  • scheduler reliability
Downstream
  • i-Ready
  • HMH instructional platforms
  • Savvas Realize
  • APEX Learning
  • other Clever-connected applications

Ownership

Owners

Technology Services, Josh Barton

Users

Educational Services, school sites, Technology Services, application owners

Aeries to Clever Rostering and SSO Hub

Operational Notes

  • The registry now treats Clever as a first-class parent hub rather than only a sub-bullet inside the broader rostering ecosystem. That is justified by three evidence layers together: an enabled Integr8r Clever job, weekly-report references to nightly Aeries-based access updates, and a current Clever-connected application inventory.
  • The hub abstraction matters because failures here are wider than one app. Roster or SSO drift in Clever can propagate to multiple instructional vendors and become classroom-visible very quickly.
  • Clever is both technical sync runtime and a governance control point: app assignment, vendor enablement, and district data-sharing controls directly shape downstream access outcomes.
  • Parent/child positioning: this page is the Clever hub child under the broader district rostering ecosystem; child pages represent specific vendor workflows, while inventory-only apps remain context entries until they need first-class runbooks.
  • Site/scope context: districtwide student and staff instructional-access distribution across Clever-connected applications.
  • Atlas still needs the missing governance layer: exact scheduler, export package ownership, app-assignment approval rules, and the boundary between first-class child integrations and inventory-only apps.

Inventory-Confirmed but Not Yet First-Class

  • Benchmark
  • Renaissance
  • College Board PSAT
  • Hazel Health
  • Ellevation

Registry Alignment

  • Mapped registry entry: INT-079.
  • Registry clarified: Clever is a production instructional access hub with enough evidence to stand as its own parent record, and several child workflows now merit dedicated pages instead of generic inventory mentions.
  • Validation gaps: scheduler details, export contract, app-assignment governance, and the threshold for promoting additional inventory-only apps into first-class Atlas pages still need documentation.