A Google Docs add-on is a small piece of software that bolts new features onto the document you already work in every day. Instead of copying text into a separate website or app, you open a menu inside Google Docs and the extra tool runs right there, alongside your paragraph. Think of it like a power outlet built into the desk: Docs is the desk, and the add-on is whatever you decide to plug in.
For teachers, this is one of the most underrated parts of the Google ecosystem. Most schools live in Docs. Students draft there, teachers comment there, feedback flows back and forth there. Yet the menu that lets you extend Docs sits quietly at the top of the screen, and a lot of educators have never opened it. This guide walks through what add-ons actually are, how they work under the hood, the categories worth knowing, and how to install and manage them without creating a privacy headache.
What an add-on actually is
When people say "Google Docs add-on," "extension," or "plug-in," they usually mean the same thing: a third-party tool that Google has approved to run inside Docs. These come from the Google Workspace Marketplace, which is the official storefront. An add-on is not the same as a Chrome extension. A Chrome extension lives in your browser and can touch almost any website you visit. A Workspace add-on lives inside a specific Google app and is scoped to that app. The distinction matters for safety, and we will come back to it.
Once installed, an add-on usually shows up in one of two places. Older add-ons appear under the Extensions menu (this used to be called the Add-ons menu). Newer ones appear as an icon in the right-hand sidebar, the same vertical strip where Calendar, Keep, and Tasks live. Clicking the icon opens a panel that floats next to your document so you can run the tool and keep reading your text at the same time.
The key idea is that the add-on works on the document in front of you. A grammar tool reads your sentences and suggests edits. A citation tool inserts a formatted reference where your cursor sits. A plagiarism or AI-writing checker scans the text and returns a report. You never have to leave the page or paste anything anywhere.
How they work under the hood
You do not need to be a developer to use add-ons, but a little mental model helps you trust them.
Most Google Docs add-ons are built with Google Apps Script, a coding platform Google maintains specifically for automating and extending Workspace apps. When a developer publishes an add-on, they declare exactly what it is allowed to do. Those declarations are called scopes, and they are the heart of the permission screen you see during installation.
A scope might say "read and change the contents of this document" or "see your email address" or "connect to an external service." When you click Install and then Allow, you are agreeing to that specific list. Google enforces those boundaries, so an add-on that only asked to read the current document cannot quietly reach into your Drive or your inbox.
Here is the workflow in plain terms. You open the document. You launch the add-on. The add-on reads the text it has permission to read. If it needs to do heavy processing, such as running an AI-writing analysis, it sends the text to the company's servers, gets a result back, and displays it in the sidebar. Some lightweight add-ons do everything locally without sending anything out. The permission screen is your clue about which kind you are dealing with. If an add-on asks to connect to an external service, assume your students' words may leave Google's servers, and check the provider's privacy policy before you roll it out to a class.
The types worth knowing
Add-ons cluster into a handful of practical categories. You do not need all of them. Pick the two or three that solve a problem you actually have.
Writing and feedback tools. Grammar and style checkers are the most common. They underline issues and propose rewrites inside the doc. For teachers, the value is less about fixing your own writing and more about modeling revision for students who can see suggestions appear in real time.
Citation and research tools. These insert formatted references in MLA, APA, or Chicago, and some pull in source details automatically. They save the part of essay writing that students dread and get wrong most often.
Integrity tools: plagiarism and AI-writing detection. This is where a platform like Checkmark fits. Rather than asking students to export a file and upload it to a separate portal, an integrity add-on lets a teacher run a check on the open document and read the report in the sidebar. The friction drops to almost nothing, which means checks actually happen instead of being skipped on a busy day.
Accessibility and language tools. Text-to-speech, translation, and readability scorers help you support multilingual learners and students with different needs without buying separate software.
Workflow and formatting tools. Mail merge, table of contents builders, diagram inserters, and template managers fall here. They are quiet time-savers for the administrative side of teaching.
A quick install walkthrough
Installing an add-on takes about a minute.
- Open any Google Doc.
- Click Extensions in the top menu, then Add-ons, then Get add-ons. This opens the Google Workspace Marketplace.
- Search for the tool you want, or browse by category. Read the reviews and the listed permissions before you commit.
- Click Install, then Continue, and sign in with the Google account you want it attached to.
- Review the permission screen carefully. This is the single most important step. If the scopes feel broader than the job requires, stop and reconsider.
- Click Allow. The add-on now appears under Extensions or as a sidebar icon.
To use it, open the Extensions menu or the sidebar, pick the tool, and follow the panel that opens. To remove an add-on later, go back to Extensions, then Add-ons, then Manage add-ons, find the tool, and choose to uninstall it.
Common misconceptions
"Add-ons can read everything in my Drive." Not unless they explicitly asked for that scope and you agreed. Most document add-ons are limited to the file you have open. The permission screen is the contract, and it is specific.
"Add-ons and Chrome extensions are the same thing." They are not. Chrome extensions run in the browser and can touch many sites. Workspace add-ons run inside a Google app and are scoped to it. When safety matters, prefer the Marketplace add-on over a browser extension that does the same job.
"If it is in the Marketplace, the school is fine to use it." Marketplace listing means Google approved the technical behavior, not that the tool meets your district's privacy rules or laws like FERPA and COPPA. Student data is a separate question. Always check whether the provider signs a data agreement your school accepts.
"Students can install whatever they want." In a managed Google Workspace for Education domain, administrators control which add-ons are allowed. If yours is locked down, an add-on you want may need an admin to approve it first. That is a feature, not a bug.
A short FAQ
Do add-ons cost money? Some are free, some are freemium, and some are paid or require a school subscription. The Marketplace listing says which.
Will an add-on work on the mobile app? Most are designed for Docs in a desktop browser. Mobile support is limited, so plan classroom use around laptops or Chromebooks.
Can an add-on change my document without asking? Only within the scope it requested. A tool with edit permission can insert or change text when you tell it to. It cannot act on documents you never opened it in.
What should an administrator do first? Decide on an allowlist. Approve a small set of vetted add-ons for the domain, confirm each provider's data handling, and tell staff which tools are blessed. A short approved list beats a free-for-all every time.
The takeaway is simple: the most powerful upgrade to Google Docs is already built in, hiding behind the Extensions menu, and the only real skill is learning to read a permission screen before you click Allow.