Project Atlas AetherDev project hub
Atlas project production

i-Ready Clever Rostering and SSO Configuration

Keep i-Ready access aligned through Aeries and Clever configuration so eligible students and teachers receive timely instructional access.

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

Purpose

Keep i-Ready access aligned through Aeries and Clever configuration so eligible students and teachers receive timely instructional access.

Current state

The registry now elevates i-Ready from inventory context to a first-class child workflow based on explicit weekly-report evidence for automatic rostering and SSO through Clever.

Next step

Confirm current districtwide scope, named business owner, and whether any direct vendor rostering now supplements Clever.

Interfaces

Inputs
  • Aeries roster and identity data
  • Clever or vendor configuration
  • site or program scope rules
Outputs
  • i-Ready access readiness
  • rostered student and teacher accounts

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 remains canonical for roster and identity source data.
  • Clever or the vendor platform reflects downstream access state and should not silently become the source of truth for SIS records.

Safe handling

  • Limit vendor admin access and exported roster artifacts.
  • Treat student and teacher roster data as restricted instructional data.
  • Document scope and approval expectations before expanding to new sites or programs.

Operational notes

Reliability posture

The child workflow matters because access drift quickly becomes classroom-visible, but owner, cadence, and launch-path details are still not centralized.

Observability

  • vendor-admin checks
  • site access incidents
  • wrapper or upload runtime evidence where available

Security and privacy

Instructional roster and access data remain restricted student and staff records and should stay within approved vendor-sharing boundaries.

Dependencies

Upstream
  • Aeries data quality
  • Clever configuration
  • vendor-side app readiness
Downstream
  • teacher and student access to the platform

Ownership

Owners

Technology Services

Users

Educational Services, school sites, Technology Services

i-Ready Clever Rostering and SSO Configuration

Operational Notes

  • Weekly-report evidence anchors this child record in a concrete onboarding case for BOHS Special Education, with later inventory evidence confirming the app remains in the active Clever-connected set.

Registry Alignment

  • Mapped registry entry: INT-080.
  • Registry clarified: this child workflow now has enough production-backed evidence to justify a dedicated Atlas page instead of remaining only inventory context.
  • Validation gaps: current site scope, business owner, and whether Clever remains the full current path still need confirmation.