Forum Discussion
Allowing microphone access on embedded web app
I have embedded a web app into my Storyline via a web object, and do not seem to be able to find any way to allow the Storyline to access the user's microphone.
How do I go about allowing the embedded page to access the user's microphone?
13 Replies
- DanAdams-9ad8e6Community Member
JoseTansengco After some testing and changes I have been able to get an iframe to request microphone access - but it does not transmit the audio from the mic to the iframe. This is happening in both Storyline and Rise.
Is there an iframe setting that should be enabled to allow the transmission of microphone audio to the frame? Thanks in advance.
Hello DanAdams-9ad8e6,
Thank you for sharing where you are in the process!
Do you receive this error message? I'm curious if you are experiencing this same error message.
- I am seeing a Quick Start guide to modifying the API Key that could be helpful.
Looking forward to hearing from you!- DanAdams-9ad8e6Community Member
Hi there,
Thanks for the reply - but no, it is not to do with that unfortunately. That is a response on the part of the app when it is receiving no mic input.
The issue appears to be that the iframe refuses to receive audio - and this occurs on both Rise and Storyline when published as an uploadable LMS package. While it works in Rise's builder and preview it still fails when it is a package uploaded to an LMS.
Any info/solutions are highly appreciated, thank you for your time so far.
- DanAdams-9ad8e6Community Member
Hello,
Thanks for the info - however, I cannot find where these iframes would be added. Where in the package should I be adding these permissions?
Hi DanAdams-9ad8e6,
I'm happy to help!
Could you please share your current iframe code in this thread? It will be helpful to see the existing code along with your .story file in order to recommend placement!
Looking forward to hearing from you!
- DanAdams-9ad8e6Community Member
Hello,
I would love to - if I knew where to find it! Could you please advise on exactly which file the iframe code can be found in? In the meantime, here is the slide/web object in question.
Thanks in advance!
Hi DanAdams-9ad8e6,
Happy to help!
You can try modifying your iframe to add the allow tags and specify the exact permissions you need. Example:
<iframe src="..." allow=”autoplay; microphone”></iframe>
Hope this helps!
- DannyMcGee-3972Community Member
Hi, I am experiencing a similar issue. I have a web app that I am running through the web object option in Storyline. When I publish and run in preview I'm getting this message.
"The security policies of this page don't allow using the microphone." I'm unsure if this is related to the page or to Storyline and would appreciate some advice.
- MichaelZCommunity Member
I've been working on exactly this problem - enabling microphone access for embedded web apps in Storyline 360.
The core issue is that Storyline's Web Object creates an iframe without the allow attribute, so the browser blocks microphone access. The fix is a JavaScript trigger that finds the iframe after it loads and adds the permissions:
setTimeout(function() { var iframe = document.querySelector('iframe[src*="YOUR_DOMAIN"]'); if (iframe) { iframe.setAttribute('allow', 'microphone; camera; autoplay'); console.log('Permissions enabled'); } }, 500);Set this as an Execute JavaScript trigger on Timeline Starts for the slide containing the Web Object. Replace YOUR_DOMAIN with whatever domain your embedded app is on.
A few things to be aware of:
- This works in published output and Storyline preview, but not in Review 360 (Review 360 has its own iframe restrictions)
- The host page must be served over HTTPS for the browser to allow microphone access
- If the iframe takes longer to load, increase the timeout from 500 to 1000 or 2000
- Test in Chrome, Firefox, Edge — they all handle this slightly differently
I wrote up the full implementation including troubleshooting common issues here: https://www.zenobits.co.uk/docs/zenobits-storyline-integration-guide (see the microphone permissions section specifically)
Related Content
- 1 year ago
- 8 months ago