> For the complete documentation index, see [llms.txt](https://participanthelp.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://participanthelp.dscout.com/interview-studies/interview-troubleshooting/interview-camera-and-microphone-permissions-and-access-troubleshooting.md).

# Interview camera and microphone permissions and access troubleshooting

In order to participate in a desktop interview study, you'll need to grant Dscout permissions to your computer's camera and microphone.

### Granting camera and microphone permissions

The first time you access the Interview pre-test on a new computer, a dialogue box will automatically pop up asking you give app.dscout.com permission to use your **Microphone** and **Camera**. Click **Allow** for both. See below:

<img src="https://content.gitbook.com/content/WDOo5BT5iAW9nWsfYLgS/blobs/zM5cyeJs7Vp5t2eBxy2p/35669618149012" alt="" width="563">

<img src="https://content.gitbook.com/content/WDOo5BT5iAW9nWsfYLgS/blobs/J1Z7PwWjCRia15zFmHQa/35669621604500" alt="" width="563">

### Troubleshooting camera and microphone permissions

If you've clicked on the **Begin Setup** button, but the permissions prompts don't show up, try clicking on the **Lock** icon to the left of the address bar or the **Camera** icon on right side of the address bar. See below.

<img src="https://content.gitbook.com/content/WDOo5BT5iAW9nWsfYLgS/blobs/YrOzpGPKWmfSAIBVBWez/35669621604756" alt="" width="563">

<img src="https://content.gitbook.com/content/WDOo5BT5iAW9nWsfYLgS/blobs/bfL0aKyje33Q2aIAcS7e/35669618150676" alt="" width="563">

Clicking these options should either open up the permissions dialogue box or show that your camera or microphone has been blocked. In the event that clicking the **Lock** icon doesn't surface the permissions dialogue box, please restart your Google Chrome or Microsoft Edge web browser and try again.

### Managing Web Browser Permissions

As an extra precaution, we recommend taking the following steps to make sure permissions are not blocked for Dscout in your web browser:

1. Open a Google Chrome or Microsoft Edge web browser window.
2. At the top right next to your address bar, click on the **More** icon (the three dots icon).
3. Click **Settings** at the bottom of the dropdown menu.
4. Google Chrome users:
   1. Click **Privacy and security**
   2. Click **Site Settings**.
   3. Click **Camera or Microphone**.
   4. Check if app.dscout.com is blocked for Camera and Microphone. If it is, remove the existing exception by clicking on the **Delete** icon to the right of the site.
5. Microsoft Edge users:
   1. Click **Cookies and Site Permissions**
   2. Click **All Sites**
   3. Locate dscout.com and verify that camera and microphone permissions are set to **allow**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://participanthelp.dscout.com/interview-studies/interview-troubleshooting/interview-camera-and-microphone-permissions-and-access-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
