For IT and administrators
Requirements
- Chrome 116 or later, on Chromebooks, Windows or macOS.
- Teachers need edit access to the documents they analyze. Google Classroom gives teachers edit access to student work that's been turned in.
Installing for teachers
Docly is published as a private Chrome Web Store item, visible only to accounts in the district's Google Workspace. To install it for a group of teachers:
- In the Google Admin console, go to Devices › Chrome › Apps & extensions › Users & browsers.
- Choose the organizational unit. Try a small test unit first.
- Click + › Add Chrome app or extension by ID, enter Docly's extension ID from its Chrome Web Store listing, and set Force install + pin to browser toolbar.
Teachers need to be signed in to Chrome with their district account. Anyone who loaded a test copy of Docly by hand should remove it, or they'll have two.
Permissions and why Docly needs them
| Permission | Why |
|---|---|
| Side panel | Docly's interface is a side panel next to the document. |
| Scripting | When a teacher clicks Analyze, Docly runs its own packaged code in that Google Docs tab to request the document's version history with the teacher's sign-in. |
| Storage | Saves the teacher's settings, and the version-history request format that worked last time (no document IDs, access tokens or content). The printable report is handed to Docly's report page through temporary session storage and deleted as soon as the page opens. |
| docs.google.com | The only site Docly talks to. It reads the version history of the document the teacher is viewing. A small script on Google Docs pages notes which version-history addresses Docs itself uses, and keeps that list in page memory only. |
Docly runs no code from outside its package, loads nothing from other sites and has no servers. It uses no AI services. The privacy policy has the details.
Updates
New versions are published to the same Chrome Web Store item. Force-installed copies update automatically, usually within a few hours of Google approving the update. The installed version shows on chrome://extensions and in the first line of the diagnostics.
Troubleshooting
| What the teacher sees | What to do |
|---|---|
| "Google refused access to this document's version history" | The teacher can only view or comment. Get edit access, or open the copy turned in through Classroom. If they're signed in to several Google accounts, they should open the Doc with the account that can edit it. |
| "Google returned a sign-in page instead of version history" | The teacher's Google session has expired, or they're signed in to the wrong account. Sign in again and retry. |
| "Google rejected Docly's request…" | In the Doc, open File › Version history › See version history and wait for it to load. Close it and click Analyze again: Docly copies the request format Google is using. |
| "Google couldn't find version history at the address Docly uses" | Google may have changed how version history loads. Send the diagnostics so Docly can be updated. |
| "Docly could not run in this tab" | Reload the Google Doc and try again. |
| A warning at the top that Docly's rebuilt copy doesn't match Google's | Some numbers may be off for this document. Send the diagnostics. |
| Editors show as "Editor 1", "Editor 2" | Google didn't share names for this document. The numbers are unaffected. |
Diagnostics
At the bottom of the side panel, Diagnostics › Copy diagnostics copies a troubleshooting report: the version-history requests and their results, counts, timings and how Docly read the history. It never includes document text, access tokens, document IDs or account IDs, so it's safe to send. Send it to the contact address in the privacy policy.