How to Enable Restricted Permissions in HarmonyOS Next Apps in 2026

Photo by FlyD on Unsplash

Introduction

Have you ever built a HarmonyOS Next app that needed access to sensitive user data like contacts or accessing audio files, only to find your permission requests silently failing at runtime? HarmonyOS Next enforces a strict permission model to protect user privacy, and certain capabilities, known as restricted permissions, require explicit approval from Huawei before your app can legally use them. Without this approval, features that depend on permissions such as ohos.permission.READ_CONTACTS or ohos.permission.WRITE_CONTACTS will be blocked on user devices.

In this guide, we walk through the complete process of requesting and enabling restricted permissions for your HarmonyOS Next applications using AppGallery Connect. Whether you are building a social app, a voice recorder, or a productivity tool, understanding this workflow is essential to avoid last-minute delays before release.

Understanding Restricted Permissions in HarmonyOS Next

HarmonyOS Next classifies permissions into two main categories: normal permissions and restricted permissions. Normal permissions (e.g., internet access) are granted automatically at install time and do not require user intervention. Restricted permissions, on the other hand, involve access to personally identifiable information (PII) or sensitive device capabilities. Because of the higher privacy risk, Huawei requires developers to submit a formal request through AppGallery Connect and receive explicit approval before these permissions become functional.

Examples of restricted permissions include:

• ohos.permission.READ_CONTACTS: Read the user's contact list
• ohos.permission.WRITE_CONTACTS: Modify the user's contact list
• ohos.permission.READ_AUDIO: Read audio files and recordings on the device
• ohos.permission.WRITE_AUDIO: Modify or delete audio files

Before you begin the approval process, ensure your application already declares the required permissions in its module.json5 configuration file:

{
  "module": {
    "requestPermissions": [
      {
        "name": "ohos.permission.READ_CONTACTS",
        "reason": "To display and manage the user's contact list"
      }
    ]
  }
}

Pro Tip: Always provide a clear, user-facing reason for each permission in module.json5. This reason is shown to users at runtime and also reviewed by Huawei during the approval process. A vague reason like "For app functionality" may lead to rejection.

Once your manifest is correctly configured, you can move on to the request workflow in AppGallery Connect.

Step-by-Step: How to Request Restricted Permissions

The entire approval process takes place inside AppGallery Connect, Huawei’s app marketplace and developer console. Follow these five steps to get your restricted permissions enabled.

Step 1: Navigate to ACL Permissions

Log in to AppGallery Connect and select the correct project and application. From the left navigation menu, go to Development and services > ACL permissions.

Development and services > ACL permissions

Accept any displayed notes or disclaimers. These outline the legal and privacy obligations associated with using restricted permissions. Read them carefully, you are committing to handling user data responsibly, and this acknowledgment is part of the formal record.

Step 2: Choose the Required Permissions

On the ACL permissions screen, you will see a list of all restricted permissions available for your app’s target API level. Select the ones your application genuinely needs.

ACL Permissions List

Pro Tip: Only request permissions that are strictly necessary for your core features. Over-requesting can delay approval and may raise privacy concerns during review. If a feature is optional, consider degrading gracefully without the permission rather than requesting access you do not fully need.

Step 3: Fill in the Usage Scenario and Request Reason

After selecting the permissions and clicking Request, a form appears asking for two critical pieces of information:

• Usage scenario: Describe exactly how your app uses each permission. For example, if you request ohos.permission.READ_CONTACTS, explain that your app imports contacts for a friend-finder feature, displays names and phone numbers locally, and never uploads contact data without explicit user consent.
• Request reason: Justify why the restricted permission is necessary. Mention alternative approaches you considered and explain why they were insufficient for your use case.

Requesting for a restricted permission

Be specific and thorough. Huawei’s review team evaluates each request against strict privacy guidelines, and insufficient detail is the most common reason for rejection. A well-written scenario not only speeds up the process but also demonstrates your commitment to user privacy.

Step 4: Submit and Wait for Approval

Once you have filled in the required fields, click Submit. The approval team typically responds within a few business days. During this time, Huawei may contact you for additional clarification, so monitor your AppGallery Connect messages and registered email address regularly.

Note: The approval can take a couple of business days, and only after the approval will the permissions be enabled.

Plan your development timeline accordingly. Starting this process early, ideally before you begin final integration testing, prevents it from becoming a blocking item close to release.

Step 5: Create a New Profile and Sign Your App

After your request is approved, the permissions are not automatically activated. You must create a new profile that includes the approved permissions and use that profile to sign your application.

1. In AppGallery Connect, navigate to Certificates, app IDs, and profiles > Profiles and generate a new profile.
2. Download the profile file (.p7b) and reference this profile on Project Structure > Signing Configs.

For detailed instructions on creating a release profile, refer to the official documentation: Requesting a Release Profile - HUAWEI Developers.

A frequent mistake at this stage is forgetting to update the signing configuration in the application after generating the new profile. Always verify that the build output uses the profile tied to the approved permissions.

Important Tips and Common Mistakes

• Start early. Restricted permission approval can take several business days. Do not leave this to the last week before your planned release. Build the request into your development timeline from the start.
• Keep your usage scenario updated. If your app’s features change after approval, for example, you add a new feature that uses a different restricted permission, you may need to submit a new request. Using permissions in ways not described during review can violate Huawei’s policies and result in enforcement actions.
• Test with the approved profile. After signing with the new profile, test your app thoroughly on a real device to confirm that the restricted permissions are functioning as expected. A common oversight is testing with a debug profile that already had permissions enabled, leading to a rude shock in production.
• Monitor permission changes across API updates. As HarmonyOS Next evolves, some permissions may move between normal and restricted categories. Revisit your ACL permissions after each target API update to ensure nothing has changed out from under you.

Conclusion

For developers, enabling restricted permissions in HarmonyOS Next is a straightforward but critical process that demands careful planning and clear communication with Huawei’s review team. By declaring permissions correctly in module.json5, submitting a detailed and honest request through AppGallery Connect, and signing with an approved profile, your app gains the sensitive capabilities it needs without compromising user trust or platform compliance. Start the approval process early, request only what your features require, and keep your usage descriptions accurate, and you will ship a secure, privacy-respecting HarmonyOS application.

References

• Restricted Permissions - HUAWEI Developers
• Requesting Restricted Permissions - HUAWEI Developers
• Requesting a Release Profile - HUAWEI Developers