Google Slides Opens but Audio Requests Access? Check the Source File Too
By ON Lab · Sources checked November 6, 2026
If someone can open your Google Slides presentation but its audio asks for access, check the underlying audio file as well as the presentation. Slides can use MP3 or WAV files stored in Drive. Review Google's access-checker suggestions for the intended audience, then verify playback using the recipient's actual permitted account.
Two files can mean two access checks
A reader shared a Slides file between a personal and school account with editing rights, yet the audio still requested access. Permission to the presentation does not by itself establish that the embedded media file is available to the same viewer.
Separate an access request from other symptoms. A missing Insert Audio feature, a file that no longer exists, a muted browser and a playback-format problem do not all have the same cause. This guide starts with the specific case where the deck opens but the audio requests permission.
1. Identify the intended recipient and source audio
Confirm which account should view the presentation. A person signed in to a different personal, work or school account may not have the same access. Do not assume that the account visible in the author's browser is the account being used by the recipient.
Locate the intended source audio in Drive. Google's current instructions support MP3 and WAV files stored there, inserted using Insert → Audio in the computer Slides editor. Verify that you are checking the file used by the affected slide, rather than another recording with a similar name.
Keep the original deck and media while investigating. Deleting and re-uploading every recording creates more uncertainty about which file each slide references. First establish the identity and availability of one affected audio file.
2. Review the presentation's access checker
Google documents an access checker that can suggest permission changes for presentations containing audio and video. Its sharing workflow is:
- Open the intended presentation on a computer.
- Choose Share.
- Add the intended people or groups.
- Choose the appropriate Editor, Commenter or Viewer role.
- Review the sharing action and any access-checker suggestion for media permissions.
- Confirm only the changes that match the intended audience and your authority.
A viewer normally does not need editing rights merely to be part of a viewing audience. Do not broaden the whole deck to editable or make every audio file public as a default troubleshooting step. Read the suggested file and recipients before confirming.
On a work or school account, organization policy can constrain sharing. If the account cannot grant the required audience access, consult the permitted owner or administrator rather than trying to bypass that policy.
3. Verify the source file and the slide as the recipient
Have the intended recipient use the account that was granted access. First establish whether that account can open the intended audio file through its permitted Drive route. Then open the presentation and test the affected slide's audio.
Do not call the problem solved because the author can play it. The useful check is whether the intended recipient can play the intended source through the presentation. If testing is not available, record recipient playback as unverified instead of treating an accepted sharing dialog as proof.
Test one affected slide before applying a broad change to a deck containing many audio files. After that check succeeds, account for the other required source files and slides individually. One working clip does not verify every recording.
4. Keep access problems separate from playback problems
- The audio still requests access: recheck the recipient account, exact source file and whether the intended permission change was saved. Escalate an organization restriction to its administrator.
- The source file is missing: identify the actual referenced file and its owner. A different file with the same name does not prove the reference is valid.
- The file opens but there is no sound: investigate playback and output conditions separately. Do not keep widening permissions when the account already has access.
- Insert Audio is absent in a managed account: ask the administrator about feature availability. This guide does not establish that sharing permissions enable a feature the account lacks.
For automatic playback or a published presentation, browser and presentation-mode behavior can add another layer. This access checklist does not guarantee automatic start, slide advancement or identical behavior on every mobile device.
5. Reopen and document the actual result
After saving the intended presentation and permission configuration, reopen the deck and repeat the relevant recipient playback check. Confirm the correct recording, not just that a speaker icon appears. For a deck with several media files, record which clips passed and which remain unverified.
Do not use a PDF export as evidence that interactive audio will play; inspect the actual delivery format you intend to use. Keep a record of the intended audience so that troubleshooting does not silently expand media access.
Completion means that the intended audience has the required access and the relevant audio plays in the checked presentation context. This guide does not access private Drive files, alter sharing, send invitations or reproduce the reader's school-account issue.