Quick answer
A browser meeting needs both operating-system access and permission for the specific website. A working camera in another app does not confirm the website has access.
Understand the issue
Open the intended meeting address directly and verify that it is the service you expect. Record whether the browser asks for camera access, reports it blocked or displays the wrong camera. Avoid resetting unrelated browser data before checking these controls.
Step-by-step checks
- Check the browser site camera permission.
- Verify Windows permits camera access for the browser.
- Select the intended camera in the meeting and preview it.
Need help with this issue?
Share your model and symptoms. Confirm availability and the quote before booking.
What the results mean
A site permission applies to that website, while Windows permissions affect the application. Check both before changing hardware.
| Stage | Action |
|---|---|
| Start | Check the browser site camera permission. |
| Compare | Verify Windows permits camera access for the browser. |
| Next step | Select the intended camera in the meeting and preview it. |
Compare the device, selected input and application settings
Identify whether the problem affects sound output, microphone input, camera video or a meeting connection. The selected device in an application can differ from the operating system default. Write down the headset, speaker or camera model and its connection type before changing several settings.
Use a simple local recording or playback test where appropriate, then compare it with the affected meeting or media app. Check mute, volume, balance and permission controls relevant to the symptom. For Bluetooth devices, call and music modes can behave differently, so test the workflow that actually fails rather than only a song or system sound.
Change one selection or permission at a time and repeat the same test. Avoid sharing recordings containing private conversations while seeking help. If a work policy controls camera or microphone access, ask the administrator rather than bypassing it. After a correction, check the intended app, sleep or reconnection behaviour and whether other required devices still work. A successful speaker test does not prove the microphone or remote participants can hear correctly.
Before you finish
- Input and output problems distinguished
- App selection compared with system default
- Local test compared with the affected workflow
- Permissions and reconnection behaviour checked
Repair checklist
If you need help, send RJ Computers your device model and the results of the checks above. Explain what must be preserved before work starts, especially files that have no other copy.
- Confirm assessment charges and what the quote includes.
- Ask for approval before additional parts or destructive software changes.
- Test the original symptom at handover and keep the repair details.
Ready for an assessment?
Share your model and symptoms. Confirm availability and the quote before booking.
Frequently asked questions
Is allowing the browser enough for every meeting website?
No. Individual websites can require their own camera permission.
What should I record before requesting help?
Record the full model, exact error or symptom, recent changes and what you already tried. Explain whether important files have a separate backup.
How do I arrange a repair assessment?
Call RJ Computers on +91 99715 24677 or use the WhatsApp booking button. Confirm availability, diagnostic fees and the scope of work before booking.
Conclusion
A site permission applies to that website, while Windows permissions affect the application. Check both before changing hardware. Keep a note of the result so a technician can continue from the evidence rather than repeat the same checks.
Further reading: Official guidance