"No permission to enable voice typing" in Google Docs

This message has four completely different causes, and the fix depends entirely on which one you hit. Most guides only cover one of them, which is why people try the same microphone setting three times and give up.

Start here: the message is almost never about your Google account. It is usually the browser refusing the microphone, not Docs refusing you.

Find your cause in under a minute

Work down this list in order. The first "yes" is your answer.

Is the address bar showing a crossed-out microphone icon? → the browser is blocking the microphone. Jump to fix 1.
Does the document say "View only" or "Suggesting" near the top right? → you do not have edit access. Jump to fix 2.
Are you in Safari, Firefox, Edge or Arc? → voice typing does not exist there. Jump to fix 3.
Is this a work or school Google account? → an administrator may have turned the feature off. Jump to fix 4.

Fix 1: Chrome is blocking the microphone

This is the most common cause by a wide margin, and the most confusing, because Chrome does not always ask you again after the first refusal. If you clicked "Block" once — even months ago, even by accident — Chrome remembers and never prompts again. Voice typing then fails silently, and Docs reports it as a permission problem.

Reset it:

Open your document.
Click the icon at the left end of the address bar (a slider, a tune icon or a padlock, depending on your Chrome version).
Find Microphone and set it to Allow.
Reload the page. Chrome will ask again the next time you start dictating.

If the microphone entry is missing from that panel, open chrome://settings/content/microphone directly and check whether docs.google.com is in the Not allowed list. Remove it there.

On a Mac, check the system layer too. macOS has its own microphone gate, and when Chrome is not allowed there, the browser's own permission looks correct while nothing records:

System Settings → Privacy & Security → Microphone → Google Chrome must be on. Turning it on requires quitting and reopening Chrome.

One more trap: the wrong input device. If Chrome has permission but picks a device that is not receiving sound — a disconnected headset, a virtual cable from a conferencing app, a monitor's built-in microphone — dictation starts and produces nothing. Check the device in chrome://settings/content/microphone.

Fix 2: You do not have edit access to the document

Voice typing writes into the document, so it needs the same permission as your keyboard. Open a file shared with you as Viewer or Commenter and the feature is unavailable — which the interface can report as a permission problem rather than as an access problem.

Look at the top right of the document. If it says View only, or the mode selector shows Suggesting rather than Editing, that is your cause.

View only → ask the owner for edit access, or use File → Make a copy to get an editable copy of your own.
Suggesting → switch the mode selector to Editing. If it will not switch, you only have comment access.

This also catches a subtler case: a document opened from a link in view mode while you are signed into a different Google account than the one it was shared with. Check which account is active in the top-right avatar.

Fix 3: You are not in Chrome

Google Docs voice typing is a Chrome-only feature. It is not in Safari, Firefox or Edge, and it is not in the Docs mobile browser. Chromium-based browsers such as Arc, Brave and Opera are inconsistent: the menu item may appear and then fail, because the speech service behind it is a Google Chrome component rather than a Chromium one.

If Tools → Voice typing is missing from the menu entirely, this is almost certainly why.

Fix 4: A Workspace administrator disabled it

On a work or school account, an administrator can turn voice typing off for the whole organisation. When that is the cause, nothing you change in your own browser will help — the setting is not yours.

Two signs point at this: the same document works in a personal Google account, and colleagues on the same domain see the same failure. The fix is a request to whoever runs your Workspace domain.

When the permission is fine and dictation still fails

Plenty of people arrive at this page having fixed the permission, only to find that voice typing still does not do what they need. That is not another permission problem — it is how the built-in feature is designed:

It stops after 10–15 seconds of silence.
Pause to think and the microphone is already off.
It stops when the tab loses focus.
Anything said while you were in another window is gone.
It does not punctuate.
You say "comma" and "period" out loud, and those commands misfire.
It has no dictionary.
Names, brands and technical terms come back wrong every single time.
It does not work in comments.
Only in the body of the document.

If that list is the actual reason you searched, the permission was never the problem.

A dictation that does not depend on the Docs menu

Google Docs Voice Typing is a Chrome extension that replaces the built-in panel. It asks for the microphone once and then stays out of the way.

Hold the right Option / Alt key inside the document and speak; release and the text lands. Two taps switch to hands-free. There is a Voice button on the page and a global shortcut (Alt+Shift+D), and the key is changeable in the settings.
Silence does not stop it. Neither does clicking into another window to check a source.
Punctuation and capitals are added for you. You can still say "new line" when you want the break exactly there.
49 recognition languages, with Auto-detect for sentences that mix two of them.
Your own Dictionary. Add names and terms once; every transcription uses them.
Works in comments, not only in the document body.
Esc discards a take you do not want; History keeps recent transcriptions so you can re-insert one.

Add to Chrome — free

Your first minute works with no account at all. Signing in with Google adds 10 more free minutes. After that it is a Pro subscription — unlimited minutes and the custom dictionary.

Worth knowing: the extension asks for the microphone from its own settings page, not from the Docs page. If you have previously blocked the microphone for docs.google.com, fix 1 above still applies — the browser-level block sits underneath everything.

FAQ

Why does Google Docs say I have no permission when I am the document owner?: Because the message usually reports a browser-level microphone block, not a document permission. Owning the file does not grant Chrome access to your microphone. Work through fix 1 first.
I allowed the microphone and nothing happened.: On a Mac, check System Settings → Privacy & Security → Microphone and make sure Google Chrome is enabled there; the browser permission and the system permission are separate gates. If both are on, check which input device Chrome selected — a disconnected headset looks identical to a permission failure.
Why is voice typing greyed out in the Tools menu?: Most often because the document is open in View only or Suggesting mode. Switch to Editing, or make your own copy.
Voice typing is missing from the Tools menu entirely.: You are not in Google Chrome, or you are in a Chromium browser that does not ship Google's speech component. Open the document in Chrome.
Can an administrator block voice typing?: Yes, on Google Workspace accounts. If the same document works in a personal account and fails in your work account, that is the cause, and only the domain administrator can change it.
Does the extension need the same permissions?: It needs the microphone, and it asks once. It does not need edit access to be granted separately — if you can type in the document, you can dictate into it.

Google Docs voice typing — full guide · Privacy policy · support@easymeetrecord.com

Google Docs and Chrome are trademarks of Google LLC. This extension is not made by, affiliated with or endorsed by Google.