Project Atlas AetherDev project hub
Atlas project production

ParentSquare Custom Contact Groups Sync

Uses Aeries-backed custom contact groups to keep ParentSquare communication segments aligned without manual list management.

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

Purpose

Support targeted communications through ParentSquare using Aeries-backed custom contact groups.

Current state

Production communications use exists, and school-specific readiness groups such as BJHS and BOHS incoming or grad-year communication groups are now treated as implementations within this parent sync rather than as standalone integrations. Exact group-rule documentation and sync timing are still partial.

Next step

Document group-definition rules, school-specific implementations, role permissions, and recurring sync cadence.

Interfaces

Inputs
  • Aeries contact data
  • group definitions
  • communications segmentation rules
Outputs
  • ParentSquare contact groups
  • communications-ready segments

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 is canonical for source contact and grouping data.
  • ParentSquare groups should mirror district-defined cohort logic.

Safe handling

  • Restrict family contact data to approved communications staff.
  • Keep group definitions and exports internal.

Operational notes

Reliability posture

Sync behavior is operationally important but logging and cadence are still lightly documented.

Observability

  • vendor-state visibility
  • manual spot checks of group membership

Security and privacy

Restricted student and family contact data; group outputs must remain internal.

Dependencies

Upstream
  • Aeries grouping logic
  • ParentSquare admin configuration
Downstream
  • targeted district and site messaging

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services, communications stakeholders, Josh Barton (owner)

ParentSquare Custom Contact Groups Sync

Operational Notes

  • The registry frames this as a real district communications workflow, not just a vendor feature toggle.
  • Custom groups reduce manual list maintenance and support targeted district communication needs.
  • BJHS and BOHS readiness-group implementations now belong to this parent record instead of being treated as standalone integrations.
  • Failure leads to incorrect or stale messaging groups and more manual cleanup.

Registry Alignment

  • Mapped registry entry: INT-018
  • Registry clarified: this is a district-owned communications sync pattern built on Aeries group logic and ParentSquare targeting, and former school-specific channel records such as INT-019 are now treated as implementation context inside this parent workflow.
  • Validation gaps: capture group rules, school-specific implementation inventory, staff-role permissions, and the actual sync cadence.