> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/android/learn-more/permissions.md).

# Android permissions

Learn about Apryse's Android SDK features and required permissions, including storage permission for accessing local documents. Follow best practices for adding permissions to your app. The Apryse And

Some features in Apryse's Android SDK require certain Android permissions, the most prominent one being storage permission for accessing documents stored locally on the device. A summary of Apryse's features and their required permission are shown below. If you need any of the specified features listed below, you will need to add the appropriate Android permissions.

## Android permissions list

| Feature                                                                                                  | Relevant permission               |
| -------------------------------------------------------------------------------------------------------- | --------------------------------- |
| <ul><li>Opening a PDF from a URL</li><li>HTML to PDF conversion</li><li>Realtime collaboration</li></ul> | `android.permission.INTERNET`     |
| <ul><li>Creating sound annotations</li></ul>                                                             | `android.permission.RECORD_AUDIO` |

{% hint style="warning" %}
**Storage Permission**

Please follow the latest Android best practices and guidelines outlined [here](https://developer.android.com/training/permissions/usage-notes/)
{% endhint %}

## Add permissions

You can add permissions to your Android app by including the `<uses-permission>` tag for the specified permission in your `AndroidManifest.xml` file. You can learn more about Android permissions in the [Android documentation](https://developer.android.com/guide/topics/permissions/overview/).

{% tabs %}
{% tab title="XML" %}
{% code lineNumbers="true" %}

```xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.pdftron.myapplication" ...>

    <!-- Permissions are added in the manifest tag -->
    <uses-permission android:name="android.permission.INTERNET"/>
    <uses-permission android:name="android.permission.RECORD_AUDIO" />

    ...
</manifest>
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# 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://docs.apryse.com/android/learn-more/permissions.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.