Skip to main content

Requesting an App for Class or Testing

If you need a specific app installed on student Chromebooks for a class, project, or test, submit a request to Academic Technology. This page covers what to send, what qualifies, and what to expect.

This process is for free apps, or apps already covered by an existing UPrep subscription — the kind of request that just needs installing, not budget approval. If you need a new tool that requires a new paid license for ongoing department use, that goes through the annual Software Process instead, not this page. If you're not sure which applies, email June and she'll point you the right way.

If what you actually need is a Chrome extension pushed to student browsers (rather than an installed app), see Requesting a Chrome Extension for Student Laptops instead — the review process is similar, but they're handled separately.

How to Request an App

Email June Peters with:

  • App name and a link to it (Play Store or Chrome Web Store)
  • Why you need it — what it's for and why an existing supported tool won't do the job
  • When you need it — the date the app needs to be installed and ready for use, not just "soon" (must be at least 2 weeks out)
  • Which students — grade level(s) or class sections that need it

Requests require two weeks' advance notice. Installing an app on student Chromebooks means pushing it through UPrep's device management console, and depending on the app, it may need a privacy and compliance check first. Two weeks gives us enough room to review the request and get it installed before you need it — requests submitted with less notice may not be ready in time, especially near a test date.

How Requests Are Reviewed

Every app is checked for:

  • Cost — confirming it's genuinely free or already covered by an existing UPrep subscription; if it turns out to need a new paid license, we'll redirect the request to the annual Software Process instead
  • Permissions requested — apps asking for broad device or account access get closer scrutiny than ones with narrow, obvious permissions
  • Vendor reputation — whether it's a known education vendor with a clear privacy policy

Straightforward, free, well-known apps are usually approved directly by Academic Technology. Anything unclear or requesting broad data access is brought to ILT for a decision, which can take longer — another reason to send requests as early as possible, well ahead of the two-week minimum if you can.

What Happens Next

  • Approved: the app is pushed to the relevant Chromebooks through UPrep's device management console. Installs typically apply the next time the device restarts or syncs — plan for that when picking your "need it by" date.
  • Denied or needs changes: you'll hear back with the reason (usually privacy, permissions, or cost) and, where possible, a suggested alternative.

Make Sure Students Are Signed In With Their UPrep Account

UPrep can only push an approved app to a device when the student is signed in with their @universityprep.org account, not a personal Gmail account. Before your app is scheduled to arrive, it's worth reminding students (and letting families know, if relevant) to make sure their UPrep account is set up and signed in on their Chromebook — see Chromebook Access Control for how the UPrep account relates to a student's personal account on the same device.

If a student's Chromebook is configured to block the UPrep account — for example, if a parent has restricted sign-in to certain accounts on the device — the automatic push install won't reach that Chromebook at all. In that case, the student will need to install the app manually, and depending on the family's Google Family Link settings, may need a parent's approval through Family Link before the install will go through. If a student is not able to resolve this issue, have them (or their family) reach out to June so it can be resolved.

Questions about an existing request, or an app that isn't installing or working as expected, should also go to June Peters.