Skip to content
English
More support Customer portal Sign in
  • There are no suggestions because the search field is empty.

Safety Threshold: protect against unexpected bulk changes

Automatically hold a sync for review when roster changes exceed a percentage limit you define

Safety Threshold automatically pauses a sync when the percentage of updated or deleted records exceeds a limit you set. The existing data remains active until all required stakeholders approve the change.

Use this when you want syncs to run automatically under normal conditions but need a safety net against accidental bulk deletions or unexpected mass updates from your SIS or other data sources.

Note: Safety Threshold is disabled when Data Preview Mode is enabled on the same application. See Data Preview Mode: approve syncs before they apply if you need to review every sync manually, not just exceptions.

How it works

  1. The data sync run initiates either automatically on a schedule or when manually triggered by an administrator.
  2. The sync engine evaluates the total volume of data modifications against predefined organizational safety margins.
  3. If the changes fall within the threshold, the system applies the updates automatically to the live environment without requiring administrative action.
  4. If the changes exceed the safety threshold, the system halts the sync operation and updates the status to Changes Pending Approval.
  5. If the changes exceed 90% of any single entity type, the system automatically flags the run for high-impact escalation and notifies SchoolDay Support.
  6. Authorized administrators—including you, the Vendor Admin, and a SchoolDay Service Operator (if escalated past 90%)—review the pending data changes.
  7. If all required parties accept the modifications, the sync resumes processing and applies the changes to the system.
  8. If any party declines the modifications, the system aborts the sync, leaves the existing data completely unchanged, and requires a new sync to be manually triggered to try again.

Requirements

  • Primary District Admin permissions
  • Import application must be activated.

Configure district thresholds

  1. In SchoolDay Connect, select your import application.
  2. Click the Settings icon.
  3. Select the Delivery Config tab.
  4. Click Advanced Settings.
  5. In the Sync hold threshold:
    • Enter a percentage value (1–100) in the Update threshold field.
    • Enter a percentage value (1–100) in the Delete threshold field.
  6. Select Save.

The threshold is now active. Syncs that exceed either value will be held automatically for your review.

To disable a threshold, set its value back to 0.

How the threshold is calculated

Thresholds are checked per entity type, such as students, staff, enrollments, sections, and others are evaluated separately.  If any entity type exceeds its threshold, the sync is held, even if the overall volume of changes is low. 

Example: You set a delete threshold of 20%. Your district has 500 staff records. If a sync attempts to delete 110 staff records (22%), the sync is held — even if student and enrollment records are unchanged.

What counts toward each threshold:

Threshold

Counts

Does not count

Update threshold

New records + updated records

Records marked for deletion

Delete threshold

Records marked for deletion

New or updated records

Note: The first sync for a new application is never held, regardless of record volume.

What happens when a threshold is triggered

  1. The application status changes to Changes Pending Approval.
  2. If configured, you receive an email notification.
  3. Your existing data remains active for all connected applications until you act.
  4. The Data Quality tab updates so you can review the incoming changes before deciding.

SchoolDay also notifies the Vendor Admin for each connected application. The sync is applied only after both you and the Vendor Admin have accepted.

Note: If changes exceed 90% of any entity type, a SchoolDay Service Operator must also approve before the sync is applied. This is a system-level safeguard you cannot override.

Review and approve a held sync

  1. Open the application and select the History tab.
  2. Locate the sync entry marked Safety Threshold is reached.
  3. Audit the pending data payload:
    1. Select Show Changes to launch the Significant Changes Summary, which provides a granular breakdown by entity type and percentage (e.g., Student - 600 (75%)). You may approve or decline the sync directly from this view.
    2. Select Browse Data to navigate to the Data Quality tab and inspect the staged dataset in its entirety.
  4. Select Accept to approve your portion, or Decline to reject the sync.

After all required parties accept: The new data is applied and the sync status updates.

After any party declines: The sync status changes to Aborted. Your existing data is not affected — it remains exactly as it was before the sync ran. A new sync must be triggered to try again.

All decisions are logged in the History tab.

Set up email notifications

  1. Go to District Administration > Default Email Notifications (to set for all district admins in your organization), or open My Profile > Email Notifications (for you only).
  2. Enable notifications for Safety Threshold events.

You receive an email when:

  • A threshold is triggered and a sync is held
  • A stakeholder declines a held sync
  • All required parties accept and the sync is applied

Verify your threshold is active

  1. Open the application and go to the Application Settings > Delivery Config > Advanced Settings.
  2. Confirm your threshold values are shown correctly.

If the values show 0, the threshold is disabled. Return to Application Settings > Delivery Config > Advanced Settings and re-enter your values.

Known limitations

  • Duplicate resolution is not available while a sync is pending approval. Duplicates are visible in read-only mode only.
  • School deletion does not trigger a threshold hold, regardless of your threshold settings.
  • A sync held in Changes Pending Approval stays pending until all required parties act. There is no automatic timeout.

Related articles