> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/setup-branding-info/app-permissions/microphone-permission.md).

# Microphone Permission

### <mark style="color:green;">What is Microphone Permission?</mark>

When your application needs access to the microphone for the purpose of recording, you need to enable this permission. \
\
Your app will ask Microphone Permission to users when requires. If user deny the permission, next time it will display and alert message to users to enable permission by going to settings.

### <mark style="color:green;">How to setup Microphone Permission?</mark>

**1.)** **Message:** This message will be displayed when first time permission will be asked. It is very important because users will be deciding to allow/deny permission based on your purpose in the message.

**2.)** **Permission Rationale Message:**  This message will be displayed user has denied the permission but the permission is required to function the app. Once the permission is denied, we cannot ask it again. So, instead we can display this rationale message. This message will be displayed as an alert popup in the app with `Settings` and `Cancel` button. Settings button will bring users to the settings of your app from where they can enable the permission again.

### <mark style="color:green;">How to test Microphone Permission in</mark> [<mark style="color:blue;">Twinr Previewer App</mark>](https://play.google.com/store/apps/details?id=com.twinr.builder.previewer)<mark style="color:green;">?</mark>

* You can test this permission in the preview app but it won't display your permission message.
* If you want to test permission with your message, you can request a build and test it.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.twinr.dev/setup-branding-info/app-permissions/microphone-permission.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.