These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Parent-Teacher Communication
- Integrations and source ownership
Integrations and source ownership
Agree how source cases and external delivery receipts are matched.
- Parent-Teacher Communication
- Source records
- Delivery channel
- Identity source
Systems to connect
- Source records. Agree the identifier and field mapping used to create each school conversation and event detail. Preserve the original source record reference.
- Delivery channel. Connect the chosen provider for authorized delivery. Retain its provider reference, receipt and outcome with the operation attempt.
- Identity source. Map authorized staff to their organization and responsibilities before allowing case or review access.
How connections are governed
Each connection needs a source owner, stable identifier and rule for retrying uncertain results. The team reviews source mappings by version and effective date when fields change. A source correction should lead to a new case revision with its prior decision and operation retained.
Reconcile delivery from the provider’s correlated receipt. When a provider gives an unknown result, inspect that original attempt before another delivery is started. Use an authorized account and keep provider credentials in the designated secret store. Prepare the pilot with a confirmed delivery and an unknown result.
Set up Parent-Teacher Communication your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.