Project Atlas AetherDev project hub
Atlas project production

Aeries Portal Accounts Sync

Maintains student portal-account readiness inside Aeries by standardizing email and creating or activating portal-account records through a semi-automated internal workflow.

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

Purpose

Maintain student portal-account readiness by standardizing email and creating or activating linked account records inside Aeries.

Current state

Production SQL maintenance exists for student email and portal-account tables through Integr8r job execution. The table-maintenance path is automated, but family-facing activation exceptions and contact-correction cases still require manual-assist handling shared between school offices and Technology Services.

Next step

Document rollback steps, guardian-side workflow boundaries, exact scheduler ownership, and the office-to-Technology Services escalation path for family-account exceptions.

Interfaces

Inputs
  • student identifiers
  • portal-account tables
  • student email conventions
Outputs
  • updated `STU.SEM`, `PWA`, and `PWS` state

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Not in scope.

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 student and portal-account tables are the authoritative state for this workflow.
  • The sync standardizes records to match district portal-account conventions.

Safe handling

  • Restrict SQL write access and account-table visibility.
  • Treat student and family-access data as FERPA-relevant.

Operational notes

Reliability posture

The SQL path is concrete, but rollback and guardian-side workflow boundaries remain under-documented.

Observability

  • Integr8r logs
  • SQL execution output
  • portal-account table state

Security and privacy

Restricted student and family-access data; internal only.

Dependencies

Upstream
  • Aeries schema stability
  • student email conventions
  • Integr8r runtime
Downstream
  • student portal readiness
  • family access workflows

Ownership

Owners

Technology Services

Users

Technology Services, school offices and family-access stakeholders

Aeries Portal Accounts Sync

Operational Notes

  • The registry shows four SQL execution steps under the AeriesPortalAccounts job.
  • Workflow mode: semi-automated. Account-table maintenance runs automatically; exception handling for parent or guardian account issues remains manual-assisted.
  • This is an internal Aeries maintenance workflow rather than an external connector.
  • Failure delays portal-account readiness and increases manual account cleanup.

Registry Alignment

  • Mapped registry entry: INT-040
  • Registry clarified: this is a concrete internal Aeries account-maintenance job with multiple table updates, not only a portal-readiness concept.
  • Validation gaps: confirm guardian-side dependencies, rollback expectations, exact run cadence, and operational ownership split between school offices and Technology Services.