Compatibility

Works With Google Workspace For Education Accounts

CQD is built for the Google Classroom interface used by schools and universities using Workspace for Education.

Account Compatibility

CQD works with both personal Google accounts and managed Google Workspace for Education accounts. School and university Classroom tenants render the same core interface as personal ones — same Classwork tab structure, same attachment cards — which is why the extension's detection works identically once it is allowed to run.

The practical gate is rarely the account itself; it is whether your school's device policy permits installing extensions in the first place.

If Your School Manages The Browser

Managed Chromebooks and school-controlled browsers can restrict what gets installed. If CQD is blocked or missing from the store on a school device, that is policy, not a technical failure. What tends to work:

  • Send your IT admin the official store link plus the open-source GitHub repository for review.
  • Point out the privacy posture: no file contents read, no third-party tracking, aggregate-only metrics.
  • Ask whether your school allows a student-requested extension allowlist process — many do.
  • On personal devices, install from the same store links with no restrictions.

Common Setups, Honestly Categorized

If your setup falls into a gray area, the fastest resolution has always been a two-line email to IT with the store link and repository URL attached. Admins respond better to transparent, auditable extensions than to any workaround — which is exactly why none is offered here.

  • Personal laptop + school Classroom account: works out of the box — this is the most common configuration.
  • School-managed Chromebook: depends entirely on your district's extension allowlist; many schools approve study tools through a request process.
  • Personal browser signed into a managed account: the browser profile is yours, so installation follows your device's rules, not Google's.
  • Teacher devices: same story as students — CQD only reads pages you already have open and downloads files already shared with you.

What CQD Never Touches

Even on managed accounts, CQD does not read your email, grades, docs, or file contents. It operates on the Classroom page you already have open, triggers downloads you could have triggered manually, and sends back only aggregate reliability counters (counts of detections and download outcomes) designed so no personal profile can be built from them.

For the full permission-by-permission breakdown, see the security overview; for data handling details, see the privacy summary.

Teachers And Admins

Teachers evaluating CQD for their classes: students using it are downloading materials you already shared with them through Classroom, via their own accounts. Nothing is posted, edited, or exfiltrated. Schools that permit "download helper" style extensions generally clear CQD quickly because the repository is public and auditable.

If you want a second opinion before recommending it to a class, point your IT department at the changelog — every feature and fix since v1.0 is documented there in plain language.

Frequently Asked Questions

Does CQD work with Google Workspace for Education accounts?

Yes. Education accounts use the same Classroom interface the extension is built against. Once installed on an allowed browser, everything — detection, Download All, flags — behaves exactly as on a personal account.

Why is the extension blocked on my school Chromebook?

School-managed devices commonly enforce extension allowlists. That is an IT policy decision, not a bug. Share the store listing and GitHub repo with your admin and ask about the school's extension request process.

Can my school see that I use CQD?

School admins can audit installed extensions on managed browsers — that is true of any extension, so install only where permitted. CQD itself reports no per-student activity anywhere.

Does it need extra permissions for school accounts?

No. Permissions are identical for every account type because the extension interacts with Classroom pages, not with account administration. Nothing education-specific is requested or stored.

Will admins consider it safe to approve?

The strongest case you can present is transparency: public source code, minimal scoped permissions, no file-content access, and documented data practices. Those four points answer most IT review checklists directly.

Classroom Quick Downloader v1.5.5 • Not affiliated with Google or Google Classroom.