Deploy the ReadingVox Chrome extension
Push the extension to every student from the Google Admin console, with your school's license key already filled in. Students get read-aloud with highlighting on any website, including Schoology, D2L Brightspace, Blackboard Ultra, Google Classroom.
Before you start
- Google Workspace admin with permission to manage Chrome apps and extensions (a super admin has it). Students must sign in to their Chromebook, or to Chrome, with their school Google account.
- Your ReadingVox license key. We email it to the account owner when your plan or pilot with Chrome extension seats starts (Institution plan with the Chrome extension add-on, or a School License). During a pilot, up to 200 students can activate until your first payment.
- The extension ID: the ReadingVox extension ID (email [email protected] for it while our Chrome Web Store listing is being finalized).
- A test student account in the same organizational unit (OU), so you can check it before students do.
Start with one OU
Install steps
Step 1: Open Apps & extensions for users
Sign in at
admin.google.com. Go to Devices → Chrome → Apps & extensions → Users & browsers. In the left panel, select the organizational unit with your students.admin.google.com/ac/chrome/apps/userOrganizational units
- yourschool.org
- Staff
- (Step marker 2)Students
- Grade 6
(Step marker 1)Users & browsersKiosksManaged guest sessionsRequestsApps and extensions installed for users in this organizational unit
(Step marker 3)+- Marker 1: The Users & browsers tab (not Kiosks or Managed guest sessions).
- Marker 2: The OU with your students. Settings apply to this OU and every OU inside it.
- Marker 3: The round + button, usually in the bottom-right corner. Hover over it for options.
Illustration — your screen may look slightly different.
Step 2: Add ReadingVox by its extension ID
Hover over + and choose Add Chrome app or extension by ID. Make sure From the Chrome Web Store is selected, paste the ID, and click Save.
admin.google.com/ac/chrome/apps/userAdd from Chrome Web Store
(Step marker 1)Add Chrome app or extension by ID
Add by URL
SourceFrom the Chrome Web Store(Step marker 2)Extension IDEXTENSION_ID (see note)Cancel(Step marker 3)Save- Marker 1: Add Chrome app or extension by ID.
- Marker 2: Paste the ReadingVox extension ID (32 lowercase letters).
- Marker 3: Save adds ReadingVox to the list for this OU.
Illustration — your screen may look slightly different.
Where's the extension ID?
Our Chrome Web Store listing is being finalized. Email [email protected] and we'll send you the ID to paste here.Step 3: Set it to Force install and add the license policy
Click ReadingVox in the list to open its settings panel on the right. Set Installation policy to Force install (or Force install + pin to browser toolbar, so students always see the icon). In Policy for extensions, paste the JSON below with your license key in place of
YOUR_LICENSE_KEY. Then click Save at the top right.Policy for extensions (JSON){ "licenseKey": { "Value": "YOUR_LICENSE_KEY" } }admin.google.com/ac/chrome/apps/userForce installReadingVox
EXTENSION_ID (see note)
(Step marker 1)Installation policyForce install + pin to browser toolbar(Step marker 2)Policy for extensions{ "licenseKey": { "Value": "YOUR_LICENSE_KEY" } }(Step marker 3)Save- Marker 1: Installation policy: Force install (pinning is optional but recommended).
- Marker 2: Policy for extensions: the JSON with your license key.
- Marker 3: Save, at the top right of the console.
Illustration — your screen may look slightly different.
The policy accepts two settings:
licenseKey(required) andapiEndpoint. LeaveapiEndpointout unless our support team asks you to set it.Step 4: Let students sign in with Google (if you restrict third-party apps)
The extension signs students in with their school Google account, so it can count license seats and read Google Docs and Slides they open. If your domain restricts third-party app access (Google does this by default for users designated under 18 in Google Workspace for Education), mark ReadingVox as trusted:
- Go to Security → Access and data control → API controls → Manage Third-Party App Access.
- Click Configure new app and search for this OAuth client ID:
31765744281-3m29c5qv6fp6l6le7fe7gkvoqfk6ktkp.apps.googleusercontent.com - Choose your students' OU and set access to Trusted.
admin.google.com/ac/owl(Step marker 1)Configure new appSearch by app name or OAuth client ID31765744281-3m29c5qv6fp6l6le7fe7gkvoqfk6ktkp.apps.googleusercontent.comReadingVox
Web application · OAuth client
(Step marker 2)Access to Google dataTrusted- Marker 1: Configure new app, then search for the client ID.
- Marker 2: Trusted, for the OU with your students.
Illustration — your screen may look slightly different.
If you skip this and access is restricted, students see a Google message saying the app is blocked when they sign in.
Check that it works
- Sign in to a Chromebook (or Chrome) as your test student. Policies can take a few minutes to arrive; to speed it up, open
chrome://policyand click Reload policies. - On
chrome://policy, ReadingVox's extension ID should be listed with alicenseKeypolicy. Onchrome://extensions, ReadingVox shows as installed by your administrator. - Click the ReadingVox icon in the toolbar. On a managed Chromebook it activates by itself with the student's Google account. If it asks, the student clicks Sign in with Google; the license key is already filled in.
- Open any article or a course in your LMS, select some text, and press play.
Each student who activates uses one seat on your license. Managed Chrome on Windows and Mac follows the same policy when students sign in to Chrome with their school account and your Admin console applies user policies to signed-in Chrome browsers.
Using it in Schoology, Brightspace, Blackboard Ultra & Google Classroom
These platforms don't have a native ReadingVox install yet, so students use the extension: they open the course in Chrome as usual and use the ReadingVox button, or select text and choose listen.
- It works on the page the student is viewing, including Google Docs and Slides they have access to.
- Some LMS content opens inside an embedded frame (for example certain Brightspace content topics or publisher tools). If a frame's text isn't picked up, open that content in its own tab and use ReadingVox there.
- The LMS mobile apps, iPads, and browsers other than Chrome aren't supported.
Troubleshooting
The extension isn't installed on a student's device
- Check the student is in the OU you configured (or one inside it), and that you set it on the Users & browsers tab.
- Have the student sign out and back in, or open
chrome://policyand click Reload policies. - The student must be signed in with the school account, not a personal Gmail account or guest mode.
Students are asked for a license key
- Check the policy JSON: the key must be under
licenseKeywith a capital-VValue, inside valid JSON (straight quotes, no trailing commas). - On
chrome://policy, confirm the licenseKey policy is listed for ReadingVox. - If Google sign-in was blocked, the key is pre-filled and the student only needs to click Sign in with Google. See step 4 to trust the app.
“Seat limit reached”
Every activated student uses a seat. During a pilot, 200 seats are available until your first payment. To add seats, email [email protected] with your school name and the number of students.
It reads with a different, robotic-sounding voice
That's the device's built-in browser voice. ReadingVox uses it for new sentences when your plan's monthly fair-use cap is reached, so students never see an error. Audio that was already generated keeps its natural voice, and the cap resets monthly.
Remove the extension
- In the Admin console, go to Devices → Chrome → Apps & extensions → Users & browsers and select the same OU.
- Click ReadingVox and either delete it from the list or set Installation policy to Block. Click Save.
- The extension is removed from students' browsers the next time their policies update (usually within a few hours, or at next sign-in).
Data & privacy
What ReadingVox receives
- When a student activates: their school email address, name, and Google account ID, to count your license seats.
- The text a student chooses to play, translate, or simplify.
- Every two weeks, a license check with a random device ID, the extension version, browser, and operating system.
What it doesn't
- Pages or text the student doesn't choose to play.
- Browsing history, grades, or messages.
- Google Docs or Slides content, except a document the student asks to hear (read-only access).
Sub-processors, retention, FERPA terms, security answers, and documents (DPA, VPAT, HECVAT Lite, W-9).
For IT & procurementOther install guides
Stuck on a step?
Email [email protected] with your platform, the step you're on, and a screenshot of what you see. We answer every message.
Email support