Project Atlas AetherDev project hub
Atlas project production

APEX Learning OneRoster Provisioning Workflow

Publish Aeries roster data to APEX Learning through the current OneRoster-style provisioning path used for instructional access.

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

Purpose

Publish Aeries roster data to APEX Learning through the current OneRoster-style provisioning path used for instructional access.

Current state

The registry now distinguishes the active `APEXLearningOneRoster` workflow from the older disabled `APEXLearning` job and from the separate API-focused component page already in Atlas.

Next step

Document exact schedule, package structure, current site scope, and the relationship between the OneRoster path and any remaining API-based enrollment tooling.

Interfaces

Inputs
  • Aeries roster and identity data
  • Clever or vendor configuration
  • site or program scope rules
Outputs
  • APEX roster payloads
  • student and teacher access 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 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
  • OneRoster packaging expectations
  • vendor ingest availability
Downstream
  • teacher and student access to the platform

Ownership

Owners

Technology Services

Users

Educational Services, school sites, Technology Services

APEX Learning OneRoster Provisioning Workflow

Operational Notes

  • This child page exists because the registry now gives the OneRoster workflow stronger production evidence than the older API component alone.

Registry Alignment

  • Mapped registry entry: INT-083.
  • 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: exact cadence, current launch pattern, and any residual API-tool dependency still need confirmation.