Skip to Main Content
Clever product updates

July product notes

July 11, 2016 Cat Kamireddy

This month we focused on improvements that will make it easier to triage any issues that may come up during the busy Back to School season, including:

  • Login tools for applications
  • Login tools for teachers
  • SIS details to help applications with troubleshooting
  • Recommended sharing settings for districts

Login tools for applications

Application support and engineering teams can now more easily triage, reproduce, and ultimately fix Instant Login issues by simulating a login as any student shared with them. This cuts down on weeks of back and forth and eliminates districts needing to share any credentials with applications.

https://www.youtube.com/watch?v=svB_QCdWNS4

Applications can check it out under the Student tab on the Data Browse page in their Clever dashboard—click on any student record to see an option to simulate their experience.

July-Product-Notes_Student-Impersonation

 

Login tools for teachers

We released a way to help teachers solve login issues in the classroom. Teachers can now generate a single-use login code for any student. The 7-digit backup code is only valid for 20 minutes after the teacher generates it, and it’s invalidated as soon as the student successfully logs in.

https://www.youtube.com/watch?v=vUOy4AQcbgI

Teachers can generate the login codes in their teacher portal, for any student’s name.

July-Product-Notes_Login-Codes

View district sync information

For districts shared with applications, the applications can also view a district’s student information system and sync type in their Clever dashboard. Surfacing this information will streamline any troubleshooting between the district and the application.

Applications can click on any district to view the SIS information, along with pause status, sharing rules, and other helpful details:

July-Product-Notes_View-Sync-Details

Recommended sharing settings

We’re making it easier to ensure districts share the right data with each of their applications— cutting down on districts sharing too little data, which results in errors, or districts “oversharing,” or sharing more information than is needed.

As applications let us know what data they recommend districts share with them, districts will only have to confirm the settings to share relevant information:

July-Product-Notes_Prevew-Rules

July-Product-Notes_Set-Rules

More to read

Khan Academy scales integrations beyond the U.S. to reach 1.75M students in Brazil
Global Partners

August 25, 2025

Khan Academy scales integrations beyond the U.S. to reach 1.75M students in Brazil

About the Brazilian Edtech Market Brazil’s edtech market operates very differently from that of the United States and Canada. Here, states—not individual schools—are responsible for purchasing and implementing digital tools. This centralized approach shapes how Brazilian education leaders ensure edtech reaches the country’s 47 million students and 2.1 million teachers across 179,000 schools (Reach Capital, […]

The Underestimated Threat: Why Student Accounts Are Targets for Cyberattacks
Districts

August 15, 2025

The Underestimated Threat: Why Student Accounts Are Targets for Cyberattacks

In the world of cybersecurity, student accounts are considered low risk because they are inside a digital walled garden. But this perception is not only outdated, it’s dangerous. Recent data from a national cybersecurity survey of school leaders reveals that one in four school organizations have seen an increase in cyberattacks targeting student accounts. Despite […]

Don’t Just Get Ready—Lead: A Proactive Edtech Approach for Back to School
Districts

July 16, 2025

Don’t Just Get Ready—Lead: A Proactive Edtech Approach for Back to School

Transform your district's edtech strategy from reactive to proactive, ensuring that your digital resources are cost-effective, instructionally sound, and secure.

Subscribe to our Cybersecure K-12 Newsletter to receive exclusive insights to safeguard school data.

This field is for validation purposes and should be left unchanged.