Introduction
If you manage student Chromebooks, you may have seen this happen: during a lesson, a student clicks Send feedback in Google Docs and sends a joke to Google instead of doing their work. It may seem like a small issue, but it can happen repeatedly.
The challenge is where the option appears. It is built into Google editors such as Docs, Sheets, Slides, and Drawings, as well as Gmail, Search, and Classroom. Since the option is part of these apps, removing it for students without affecting the tools they need for learning can be difficult.
This post shows where Send feedback appears in Google editors and apps, explains why common fixes have limitations, and shows how to prevent students from sending feedback using xFanatical Safe Doc’s BlockSendFeedback policy for the student groups you choose.
Why Disabling Send Feedback for Students Falls Short
Every Google Workspace app has a Send feedback option, including the docs editor students use most. In Google Docs, it appears under Help > Help Docs improve. Sheets and Slides follow the same pattern. Gmail, Search, and Classroom have their own feedback options. These tools let users send bug reports or comments directly to Google, which is usually helpful.
The Send feedback option circled in the Google Search Settings menu.
In a classroom, however, students use this option for fun purposes. During a lesson on a managed Chromebook, a student opens Docs, clicks Help, and sends Google a joke instead of completing the assigned work. Another irrelevant feedback message goes out during class. It may seem small, but it can happen repeatedly, taking students' attention away from the lesson each time.
The problem in short:
- Two groups feel the impact most: teachers who see the distraction during class, and IT admins who want one setting they can apply to each student group.
- The native Chrome policy controls Chrome’s own feedback tool, while the in app option remains available in Gmail, Docs, and other apps.
- Turning off an entire Google service would affect far more than feedback and disrupt the apps students use for learning.
- What schools need is a targeted fix that removes this one option for students while keeping all other app features working normally.
What Schools Tell Us
Schools rarely raise the Send feedback option on its own. They describe a wider problem: a built-in Google feature that is difficult to remove, students misusing it, and the need for one setting that admins can apply to each student group.
A K-12 IT director put the native gap plainly: “Google didn’t offer any real way to control this, so it felt like an endless game of whack a mole every time a new feature or layout appeared.” What closed it, he said, was the ability to “customize policies per OU”.
In the deployments we have supported, schools repeatedly ask for one admin setting to remove a built-in Google option from student accounts while keeping the apps students need fully functional.
The Cost of Leaving It On
Left alone, the cost is quiet, but real:
- Students send off topic or unnecessary feedback to Google during class, creating a small but repeated distraction.
- The Send feedback option remains visible in the student interface, adding clutter.
- Since the native policy leaves the option available, admins must keep addressing the same issue instead of resolving it with a single setting.
How Schools Try to Disable Send Feedback Today
Before trying an extension, schools usually check for a built in setting first. There is one option to consider, and it helps to understand what it can do and where its limits lie.
It is a chrome policy an admin can set UserFeedbackAllowed to false from the Admin Console, and on its own surface it does real work:
- It uses Chrome’s built-in management, so there is nothing extra to buy or install.
- When set to false, it stops feedback sent through Chrome’s own tools, including Report an issue in the Chrome menu and the Alt + Shift + I shortcut that opens the same feedback box.
The catch is that this policy controls Chrome’s own browser tools. It cannot change what appears inside a web page, even when the page belongs to Google. So in Google Docs, Sheets, Slides, Gmail, and other Workspace apps, the in app Send feedback option remains visible and continues to send feedback.
This creates a false sense of completion. An admin sets the policy and assumes the task is finished, but students can still see and click the in app feedback option.
Web filters offer no targeted solution either. They block entire websites, so removing one menu option would mean blocking the whole app students need.
What a Real Fix Must Do
So what would a real fix do? Five things:
- Remove the option itself: Make it disappear from the screen, leaving students with nothing to click.
- Cover feedback across supported apps: Include Docs, Gmail, Sheets, Slides, Search, and Classroom, covering the feedback options inside these apps as well as Chrome’s own feedback.
- Manage it centrally: Let admins apply the policy through the Admin Console to selected student organizational units (OUs), so students have no way to undo it and admins avoid setting it up on each device.
- Keep other features working: Remove the feedback option while leaving the rest of each app available.
- Be clear about device support: State exactly which devices are supported so schools know where the policy applies.
That is the gap Safe Doc’s BlockSendFeedback policy is built to close.
Why the native Chrome Policy Cannot Remove Send Feedback
The previous section showed that Chrome’s policy disables the browser’s own feedback tool, while the Send feedback option inside Workspace apps remains available. The key difference is where each option lives, and that distinction explains the gap this post addresses.
The Blind Spot: Why the Policy Stops at the Browser
A Chrome policy controls the browser’s own tools, including Report an issue in the Chrome menu and the Alt + Shift + I shortcut. It can turn these features off, but the content inside a web page is controlled by the app itself.
The in app Send feedback option is part of the page created by Docs, Gmail, Search, and other apps. It sits inside the app, so the Chrome policy leaves it untouched. The setting an admin changes and the option a student clicks are in two different places. To remove that option, the solution needs to work inside the app page itself.
How Safe Doc Actually Works
Safe Doc is a Chrome extension that admins configure for selected student groups. The key difference is where it works. A browser policy controls the browser itself, while Safe Doc runs a content script, according to our development team. This code works inside the app’s page and changes what appears there, allowing Safe Doc to reach the in app option directly.
When the BlockSendFeedback policy is set to true, Safe Doc removes the Send feedback options from supported apps. In Docs, Help > Help Docs improve disappears, and in Gmail, Help > Send feedback is removed. The option vanishes from the screen, leaving students with nothing to click.
Here is Neeraj Nanvani, Development Director at xFanatical, on what the policy targets:
“The restriction targets the entry points users normally use to submit feedback from supported applications. It does not disable the entire application or prevent users from using its regular features. This distinction is important because removing the feedback interface is different from applying a server-side restriction to Google’s feedback submission services.”
Two things stand out:
- Safe Doc removes only the feedback option. The apps continue working normally, and students keep access to the features they need for learning.
- Safe Doc changes what appears inside the app page instead of blocking Google services. This lets it reach the feedback option that the Chrome policy leaves untouched.
Disable Send Feedback in Google Workspace
One policy covers all supported apps. Set BlockSendFeedback to true for a student group, and Safe Doc removes the Send feedback option wherever it appears in those apps. The menu label varies between apps, so the examples below show where to find the option and how the menu looks after the policy is enabled. Each pair shows the same menu before and after Safe Doc is applied.
Block student feedback in Google Docs
In Docs, the option sits under Help > Help Docs improve. With the policy on, the entry is gone from the Help menu.
Supplied Safe Doc before and after capture, Google Docs.
Disable Send Feedback in Google Sheets
In Sheets, the entry is Help > Help Sheets improve. Once the policy is on, it no longer appears.
Supplied Safe Doc before and after capture, Google Sheets.
Block Send Feedback policy in Google Slides
In Slides, the entry is Help > Help Slides improve. Once the policy is on, it no longer appears.
Supplied Safe Doc before and after capture, Google Slides.
Block Send Feedback in Gmail
In Gmail, the option lives under the Help menu the ? icon, as Send feedback to Google. The policy removes it, leaving Help, Training, and Updates in place.
Supplied Safe Doc before-and-after capture, Gmail.
Disable Send Feedback in Google Search
In Google Search, the option is in the Settings menu as Send feedback. With the policy on, the Settings menu no longer lists it.
Supplied Safe Doc before-and-after capture, Google Search.
Block Send Feedback in Google Classroom
In the classroom, the option sits under the Help menu the ? icon, as Send feedback to Google. The policy removes it, while Help, Ask the Help Community, and What’s new in the classroom stay.
Supplied Safe Doc before-and-after capture, Google Classroom.
Step-by-Step: How to Disable Send Feedback with Safe Doc
To disable Send Feedback for students, configure the Safe Doc BlockSendFeedback policy by following these steps:
Step 1: Apply for a Free 30-day trial license key. The trial license and the sample policy configuration file will be emailed to you.
Step 2: Sign into the Google Admin Console and deploy xFanatical Safe Doc to the selected student organizational unit (OU). Full walkthrough: the Safe Doc deployment guide and the Safe Doc configuration reference.
Step 3: Go to Devices > Chrome > Apps & Extensions > Users & browsers, navigate to your Safe Doc policy configuration for the relevant organizational unit (OU).
Admin Console with Safe Doc’s BlockSendFeedback policy set to true for a student OU.
Step 4: Click the xFanatical Safe Doc app.
Step 5: In the right-hand panel, under Policy for extensions, add and edit your policy configuration JSON to include “BlockSendFeedback ”.
"BlockSendFeedback": {
"Value": true
}
Step 6: Click Save to apply the changes.
Step 7: Verify that the policy is active.
Note: Wait a few minutes for the policy to be propagated to the students' devices. This can also take up to 24 hours.
Frequently Asked Questions
- Does the native Chrome policy remove Send Feedback for students?
The UserFeedbackAllowed policy controls Chrome’s own feedback tool, Report an issue. The in app Send feedback option remains visible inside the apps, and students can still use it to send feedback.
- What is the difference between Chrome’s own feedback and the in-app option?
Chrome’s own feedback is the browser’s Report an issue option in the Chrome menu. The in app option appears inside each app, such as Help > Send feedback or Help Docs improve in the editors. These are separate features.
- Where does the Send Feedback option appear across the apps?
It appears in the Help or Settings menu of Docs, Sheets, Slides, Gmail, Search, and Classroom. Labels include Help Docs improve and Send feedback to Google. Google Drawings is covered too.
- How do I disable Send Feedback for students only?
Set Safe Doc’s BlockSendFeedback policy to true and apply it to the student organizational unit (OU). Staff and teachers in other OUs can still report genuine bugs.
- Does removing the Send feedback option break the other app features?
The policy targets the feedback options alone. Students can continue using Docs, Gmail, and the other supported apps as usual, with the Send feedback option removed.
- Which apps and devices does the fix cover?
It covers supported Google Workspace apps on managed ChromeOS, Windows, and Mac devices. Safari, Firefox, Edge, and mobile apps fall outside this support.
- How do I check it actually worked?
Sign in with a student account in the target OU and open a supported app. Check its Help or Settings menu. The Send feedback option should be gone.
Conclusion
The Send feedback option is built into the Google editors and apps students use every day, and Google’s built in controls do not remove it. Safe Doc addresses this gap. Set the BlockSendFeedback policy to true, and the option is removed from supported apps for students. Admins can apply this single setting to each organizational unit (OU) they choose, while the apps continue working normally.
This gives schools a simple way to disable Send Feedback for students and block student feedback in Google Workspace, alongside the Chrome policy they already use.
Start a free trial if you have not deployed Safe Doc yet, or contact us for help setting it up across your fleet.
Related Safe Doc guides
Use the related-article block beneath the author card:








xFanatical Safe Doc