Skip to Main Content
Clever product updates

March 2017 product release notes

March 13, 2017 Cat Kamireddy

We have two big releases this month: district user roles (in beta) and a way for apps to set their licenses for districts. And we got a little extra polish in for the district dashboard, too:

New user roles for districts

We created two new user roles for districts that use the Clever dashboard:

  • School tech leads (previously “school admins” in Clever) have some access to technical settings and can navigate to and from the Clever Portal and the dashboard to help manage schools in Clever. They can also view usage metrics, use sharing rules, and manage and print Clever Badges.
  • Curriculum managers can use Clever for non-IT related activities, but aren’t able to modify technical settings, such as Instant Login configurations or data sharing. They can see which applications are in use, see which students have app access, view login metrics, and manage links within the Clever Portal.

Learn more about the roles here. It’s currently only available to beta districts, and we’ll be rolling it out soon to all districts. If you’re interested in joining our district beta program, let us know in the comments, and we’ll reach out!

 

Available licenses for applications

Applications can now set the number of licenses for each district they connect with on Clever! Licenses can be set by either number of schools or number of students:

Right now, setting a license number doesn’t enforce a data sharing limit but highlights for both applications and their districts when licenses are being exceeded.

 

Clever Badges and school tech leads

Last month, we enabled the ability for teachers to reprint students’ Clever Badges—and now we extended that to school teach leads! School tech leads can both print and reprint Clever Badges after the feature is enabled on the district-level.

 

Updated district dashboard

We updated a few pages for districts in their dashboard to make it easier to manage their student data.

  • On the Sync Upload page, districts can upload school admin files—and upload a subset of files. Meaning, if a district only needs to change their student file, they no longer need to upload the rest of the files.
  • The Portal Settings is updated and makes it easy for districts to customize their portal URL or set a custom link. Districts can also enable or disable universal SSO, as well as the ability for teachers to use one-time login codes for students.
  • The Sync Report page also got a new look—but more importantly, it’s a lot faster! Districts that have a hold on their data will be able to review changes here.
  • And districts can access the Help Center and Clever Community from their header! Just click the question mark to access either resource.

More to read

Data Obfuscation vs. Data Minimization: A School’s Guide to Secure Data Sharing
Districts Global

March 18, 2026

Data Obfuscation vs. Data Minimization: A School’s Guide to Secure Data Sharing

Learn how Clever offers data minimization tools to help safely provision accounts for edtech applications.

The Infrastructure of Trust: Winning the United States K-12 Market in 2026
Partners

March 12, 2026

The Infrastructure of Trust: Winning the United States K-12 Market in 2026

The U.S. K-12 market has reached an inflection point. We are moving away from an era of unchecked edtech growth toward a future defined by intentional edtech. Success no longer comes from being a point solution; it requires becoming a partner in evolution. To lead in this landscape, true partners must shift their focus from […]

End password chaos: The 5-step guide to secure, age-appropriate logins in schools
Districts Global

December 23, 2025

End password chaos: The 5-step guide to secure, age-appropriate logins in schools

School IT departments — take these 5 steps to offload the burden of manual password resets while improving cybersecurity for classrooms.

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.