Getting Adobe Express into Your School — Starting From Scratch
A Plain English Guide to the K-12 Onboarding Wizard
So your school wants to use Adobe Express?. Great choice. It's a genuinely powerful creative tool for students and teachers alike — and here's the bit that often surprises people: it's completely free for K-12 schools. No budget codes, no procurement headaches, no per-seat licence negotiations. Adobe Express for K-12 is free and unlimited.
But — and this is the bit that catches schools out — "free" doesn't mean "just download it and go." You still need to set things up properly so that students log in safely, accounts are managed centrally, and your school stays in control of who has access to what. That's where the K-12 Onboarding Wizard comes in.
Before You Start — What Do You Actually Need?
This is important, so read it before you click anything. The wizard requires the IT Admin to have either a Microsoft 365 Global Admin account or a Google Workspace for Education Super Admin account. If you're the school's IT person and you don't have one of those, stop here and get that sorted first. The wizard won't work without it.
Also worth a quick check: make sure your network allows Adobe traffic. Adobe publish their network endpoints on the Help site — worth a quick scan with your firewall team before you start.
Step 1 — Fire Up the Onboarding Wizard
Head to k12.onboarding.adobe.com — that's your starting point. The K-12 onboarding wizard enables IT Admins of eligible K-12 schools and districts to deploy Adobe Express for Education to all of their users in a quick and simple process.
The wizard will walk you through creating your Adobe Admin Console — which is the control centre for everything Adobe in your school. Think of it like your Microsoft 365 Admin Centre, but for Adobe. Once the console is created, you'll need to set your organisation type as K-12 and accept the free Adobe Express offer along with the additional K-12 privacy terms on behalf of your school.
Step 2 — Sort Out Your Identity (The Bit Most Schools Rush Past)
This is the most important technical step and the one that causes the most support calls when it gets skipped.
Adobe uses Federated Identity — which is a fancy way of saying it connects your school's existing login system (Microsoft or Google) to Adobe accounts. This means pupils and staff don't create separate Adobe passwords — they just use their school credentials.
Adobe recommends using Federated Logins to create Adobe accounts; these can be created on a user's first login or by syncing user details from your directory.
In the Admin Console, go to Settings → Directory and set up your federation. If your school runs Microsoft 365, you'll connect via Azure/Entra. Google Workspace schools connect via Google Federation. You'll also need to confirm you have claimed all of your school's domains in your Federated Directory — and if your domains are nested in another directory, you'll need to move them.
Don't skip the domain claiming step. If your school email domain isn't claimed in your console, students signing in with those addresses won't be recognised properly.
Step 3 — Choose How Users Get Their Accounts
Once identity is set up, you need to decide how students and staff actually get their Adobe accounts. There are three main options:
Microsoft 365 / Entra Sync gives you automatic user management, automatic licence management and deprovisioning, group-level Generative AI controls, and role sync. Google Workspace Sync gives you the same automatic management using Organisational Units. Just-in-Time provisioning is the simplest option — users get a licence automatically the first time they log in, with no sync required, though you'll need to clean up leavers manually.
For most UK schools on Microsoft 365, Entra Sync is the recommended route — set it up once, and it keeps itself up to date as staff and pupils change.
Step 4 — How Will Users Actually Sign In?
Beyond the technical federation, you want login to be as frictionless as possible for teachers and pupils. Adobe supports a range of single sign-on pathways, and you can have as many enabled as you like without causing conflict.
For UK schools, the most common options are:
- Microsoft SSO via Entra (most secondary schools)
- Google SSO (many primary schools on Google Workspace)
- Clever or ClassLink (mainly US-focused, but available)
- Canvas or Google Classroom integration if you use those as your LMS
One practical tip: make sure you've placed the Adobe Express icon at the top of your school portal app list so it is easy to find. It sounds obvious, but the number of schools that deploy software and then wonder why nobody uses it is genuinely staggering.
Step 5 — Think About Devices
A couple of device-specific things worth knowing before you declare victory:
Chromebooks — there is no native Chromebook app, so Adobe recommend pinning the Adobe Express web app to the Chromebook taskbar. iPads — deploy the Adobe Express app through your MDM to ensure students with iPads can access the tool.
Windows and Mac devices just need a browser — no installation required for the web version.
Step 6 — The Bits You Shouldn't Ignore
Before you wrap up, three things that are easy to skip and cause problems later:
Domain Enforcement. Make sure Domain Enforcement is turned ON to prevent personal accounts from being created with your school's domains. Without this, a student could inadvertently create a personal free Adobe account using their school email, which causes all sorts of licensing headaches.
Generative AI controls. Adobe Express includes AI-powered features such as text-to-image generation via Adobe Firefly. You'll want to decide how you'd like students, teachers, and staff to interact with Adobe's Generative AI — and configure this at the Admin Console level before users start exploring.
Add-ons. Worth knowing: from April 2026, the Adobe Express K-12 add-on collection is turned on by default for all users in K-12 organisations. As the admin, you can manage this — enabling or disabling add-on access at the organisation or individual user level. It's not a dealbreaker, but it's worth reviewing what's included before a teacher asks why there's a third-party tool appearing in their pupils' accounts.
What About Privacy and Compliance?
Schools rightly ask about this — especially under UK GDPR. Adobe does publish a full set of documentation covering their Student Privacy Policy, Data Processing Addendum, and sub-processors list. These are available from the Adobe Trust Centre and should be reviewed by your Data Protection Officer before rollout. Not the most exciting reading, but important if you're a school with obligations under GDPR and the ICO's guidance on EdTech.
Summary — The Quick Version
If you just want the checklist:
- Confirm you have a Microsoft 365 Global Admin or Google Workspace Super Admin login
- Go to k12.onboarding.adobe.com and complete the wizard
- Set up Federated Identity and claim your school domain(s)
- Choose your user sync method (Entra, Google, or Just-in-Time)
- Set up your preferred login pathway(s)
- Turn on Domain Enforcement
- Configure Generative AI settings
- Pin Adobe Express to your school portal or device launcher
- Test a student login before telling anyone it's live
The whole process, if your Microsoft or Google admin access is ready and your domains are clean, can realistically be done in a morning. The wizard is well designed — Adobe have clearly put effort into making this accessible for school IT staff who aren't Adobe specialists.
And once it's running? Your teachers and students get access to one of the best creative tools in EdTech. For free. That's a pretty good return on a morning's work.
Questions about deploying Adobe Express at your school? Feel free to drop a comment below, or get in touch with me sai73158@adobe.com — we support schools across Norfolk and beyond with Adobe deployments and training.
Comments
Post a Comment