Adobe Express on Chromebooks — Are Your Students Actually Logging In Properly?

 Adobe Express on Chromebooks — Are Your Students Actually Logging In Properly?

If your school has Chromebooks and you are using Adobe Express, there is a question worth asking your IT admin this week. Are your students logging in seamlessly, or are they hitting a wall asking for an email verification code they can never actually receive?

I have been speaking with a number of schools recently and this comes up a lot. Teachers set up their Adobe Classrooms, share the class code with students, and then nothing works quite right. Students can't join, or they get stuck in an email verification loop, or everyone ends up sharing one account just to get anything done. If this sounds familiar, the issue is almost certainly how Adobe Express has been deployed, not anything the teacher has done wrong.

The root cause

When Adobe Express doesn't recognise a student as a properly provisioned user, it falls back to email verification to confirm who they are. For primary school students, or any students who don't have individual email access, that's a dead end. The shared account workaround that schools end up using causes its own headaches — projects getting mixed up, syncing problems, and no way for a teacher to see which student did what.

The fix — Google App Licensing

Adobe and Google have built a proper solution for exactly this scenario. It's called Google App Licensing, and for Chromebook schools it's the right way to deploy Adobe Express.

The way it works is straightforward. Your IT admin sets up Adobe Express licenses through the Google Admin Console rather than purely through the Adobe Admin Console. Once it's configured correctly, students simply open their Chromebook, click the Adobe Express icon, and they are signed straight in using their existing Google school login. No codes. No email verification. No friction. The Chromebook already knows who the student is, and Adobe just trusts that.

The key things the IT admin needs to check are that Google SSO is configured in the Adobe Admin Console, and that auto-account creation is switched on in the directory settings. Without that second setting enabled, Adobe doesn't automatically create an account for students on first login, which is what triggers the whole verification loop.

Once it's working, each student has their own individual Adobe Express account tied to their school Google login. Their projects are theirs, they can join Classrooms properly using the class code their teacher shares, and teachers can actually see individual student work and progress.

It's free and it's already available

Worth emphasising — this isn't an add-on you pay for. Adobe Express for K-12 is free, and Google App Licensing is part of that. Schools that already have Adobe Express set up through the Adobe Admin Console can still move to Google App Licensing without losing their existing setup. Nothing changes from the user's perspective, it just works properly.

What to do next

If you are a teacher and this sounds like your situation, the conversation to have is with your IT admin rather than trying to fix it yourself. Point them at Adobe's Google App Licensing deployment guide and ask them specifically to check whether Google SSO and auto-account creation are both enabled in the Adobe Admin Console.

If you are an IT admin reading this and you want a hand working through the setup, feel free to get in touch. It's a relatively quick fix once you know what to look for, and it makes a significant difference to how usable Adobe Express actually is in the classroom day to day.