Skip to content
English
  • There are no suggestions because the search field is empty.

November 2026, Release Notes

Features

Admin accounts without a password step on the new authentication engine

Audience: District Admins

Admins on the new authentication engine can now create new administrators with only a name and email address. The new admin receives an email invitation to set their own password, so nobody has to create, send, or reset a password for them. The Create Administrator screen no longer requires a password for migrated districts. Districts that haven't moved to the new authentication engine keep the current form.

See Create and manage administrator roles

Restore default attribute mapping

Audience: District Admins

Admins can now click Restore default mapping in the Attribute mapping section of an SFTP or API import application to return the mapping to the default for its data source type in one step, instead of correcting fields one by one after a mistake. A data source already on the default mapping is left unchanged.

Updates

View-only access for District Admins without Primary permissions

Audience: District Admin

District Admins without Primary permissions now have view-only access. They can view all district data, download existing files, and manage their own password, MFA, and notification preferences. They can no longer run syncs, change sync schedules, filters, mappings, or delivery settings, resolve duplicates, manage data-sharing requests, or create, edit, or delete admins and organizations. These actions now require Primary District Admin permissions.

If a District Admin needs to make changes, a Primary District Admin can select Primary Admin for them in Administration > Admins. Admins are signed out when their permissions change and see the new permissions the next time they sign in. Each district must have at least one Primary District Admin, so you can't demote or remove the last one.

SMS verification for administrators ends on the new authentication engine

Audience: District Admins

This applies only to districts migrating to the new Authentication engine. If your district is not migrating, no changes are required.

When your district migrates to the new authentication engine, administrators verify their identity with an authenticator app, and SMS codes are no longer available. Before your district migrates, set up an authenticator app, such as Google Authenticator, Microsoft Authenticator, or Authy.

After the migration, administrators sign in at sso.schoolday.com, and the MFA settings no longer appear under My Profile. See Set up MFA for your admin account.