Purpose
Automate TeachTown staff and student account management and provide SSO through Clever.
Current state
District-supported production integration exists for TeachTown access, but the authoritative source system and sync rules are still partially documented.
Next step
Document the source systems, support boundaries, and exception-handling rules.
Interfaces
Inputs- student and staff identity data
- program placement context
- Clever SSO configuration
Outputs- TeachTown account state
- Clever SSO readiness
Reality to Action trace
Reality IngestionContributes in this stage.
Canonical StorageNot in scope.
Automation EnginesContributes in this stage.
Human InterfacesNot in scope.
Operational AdoptionContributes in this stage.
Core workflow
TBD. Document the 5-10 steps that define the core workflow.
Data integrity and contracts
Source of truth rules
- District source data is canonical for user identity and access eligibility.
- TeachTown and Clever reflect downstream access state.
Safe handling
- Restrict program-access exports and admin credentials.
- Treat student program data as highly controlled.
Operational notes
Reliability posture
Production value is clear, but the exact source contract and ownership boundaries still need fuller documentation.
Observability
- vendor-admin state checks
- manual provisioning review
Security and privacy
Restricted student and staff program-access data; internal only.
Dependencies
Upstream- authoritative student and staff data
- Clever connectivity
Downstream- specialized instructional access
Ownership
OwnersTechnology Services, Josh Barton
UsersSpecial Education, Technology Services, Josh Barton (owner)
TeachTown Account Provisioning and Clever SSO Integration
Operational Notes
- The registry places this inside the active Special Education integration footprint, but it should not be flattened into generic Clever hub language. TeachTown remains a program-specific access workflow with its own support boundaries and exception handling.
- Atlas now treats Aeries to Clever Rostering and SSO Hub as the parent instructional access hub. This page is the program-specific child or adjacent workflow where Clever SSO and TeachTown account readiness meet Special Education operations.
- Failure here delays access to specialized instructional tools and shifts support burden back to manual account work.
Registry Alignment
- Mapped registry entry:
INT-020. - Registry clarified: this is an active program-specific provisioning and SSO workflow, not just a platform mention inside the broader Clever ecosystem.
- Validation gaps: authoritative source systems, recurring update cadence, support-owner boundaries, and exception-handling rules still need fuller documentation.