How to Request
Restricted permissions can be granted to third-party applications only after being approved. For details about how to apply for restricted permissions, see Requesting Restricted Permissions.
Applications that require restricted permissions will undergo a review during submission for release in AppGallery Connect. If the application does not meet the requirements, it will be rejected. For details about the review process, see Releasing a HarmonyOS App.
ohos.permission.SYSTEM_FLOAT_WINDOW
Allows an application to be displayed in a floating window on top of other applications.
Applicable scenarios and functionalities:
- Multi-party video call
- Screen sharing
- This permission is available only to PC/2-in-1 device applications.
For the window provided by the floating window, the application must also provide the user the way to exit.
Alternative solution in other scenarios: Use PiP. For details, see Using PiP in Applications.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 7
ohos.permission.READ_CONTACTS
Allows an application to read Contacts.
Applicable scenarios and functionalities:
The application needs to clone, back up, or synchronize contacts.
Example:
- The application needs to read contacts from the local address book in batches and synchronize them to the cloud server.
- The application needs to read contacts in batches and synchronize or clone them between devices.
For other scenarios, you can use the contact Picker to access contact data. For details, see Contact Selection with Picker.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: user_grant
Since: 8
ohos.permission.WRITE_CONTACTS
Allows an application to add, remove, and modify Contacts.
Applicable scenarios and functionalities:
The application needs to clone, back up, or synchronize contacts.
Example:
- The application needs to write contacts read from the cloud server to the local address book in batches.
- The application needs to write contacts synchronized from other devices to the address book in batches.
Alternative for other scenarios: Except for the preceding scenarios, applications cannot modify the contact data. Instruct the users to modify the contacts data in Contacts.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: user_grant
Since: 8
ohos.permission.READ_AUDIO
Allows an application to access the audio files in a user public directory.
Applicable scenarios and functionalities:
The app needs to clone, back up, or synchronize audio files.
Example:
- The application needs to read audio files from a public directory in batches and synchronize them to the cloud server.
- The application needs to read audio files from the public directory in batches and synchronize or clone them between devices.
Alternative for other scenarios: Use AudioPicker to access user audio files. For details, see Selecting Audio Clips.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: user_grant
Since: 9
ohos.permission.WRITE_AUDIO
Allows an application to modify the audio files in a user public directory.
Applicable scenarios and functionalities:
The app needs to clone, back up, or synchronize audio files.
Example:
- The application needs to save audio files read from the cloud server to the local public directory in batches.
- The application needs to save audio files synchronized from other devices to the local public directory in batches.
Alternative for other scenarios: Use AudioPicker to save user audio files. For details, see Saving Audio Clips.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: user_grant
Since: 9
ohos.permission.READ_IMAGEVIDEO
Allows an application to read image or video files from users' local public directories.
Applicable scenarios and functionalities:
The application needs to clone, back up, or synchronize local image or video files.
Example:
- The application needs to read files (images and videos) from the local media library in batches and synchronize them to the cloud server.
- The application needs to read files (images and videos) from the local media library in batches and synchronize or clone them between devices.
Alternative for other scenarios: Use PhotoViewPicker to access user images or videos. For details, see Selecting Media Assets Using Picker.
In the following scenarios, you do not need to apply for the permission or use the picker:
-
Without this permission, an application can read images or videos that it has written to the gallery.
-
A user manually selects an image or video in the application and processes it, for example:
(1) A user manually selects an image or video in the application and casts it to another device, such as a large screen.
(2) A user manually selects an image or video in the application and sends or shares it to another application or device.
(3) A user manually selects an image or video in the application and performs operations such as encryption and beautification on the image or video.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: user_grant
Since: 9
Changelog: In API versions 9 to 24, this permission allows an application to access images or videos stored on the cloud or locally. From API version 26.0.0, this permission allows an application to read only images or videos in users' local public directories.
ohos.permission.WRITE_IMAGEVIDEO
Allows an application to modify the images/videos in a user public directory.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Recommended solution without the permission: Use the security control or authorization dialog box to save the media resources specified by the user to the gallery. For details, see Saving Media Assets.
Permission level: system_basic
Authorization mode: user_grant
Since: 9
ohos.permission.READ_WRITE_DESKTOP_DIRECTORY
Allows an application to access the Desktop directory and its subdirectories in the user public directory.
Currently, only applications on 2-in-1 devices and tablets can request this permission.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: system_basic
Authorization mode: user_grant
Since: 11
ohos.permission.ACCESS_DDK_USB
Allows extended peripheral drivers to access the USB DDK interfaces to implement development of USB extended peripheral drivers.
Applicable scenarios and functionalities:
- The bus type of the external device to connect is USB. The external device connected can implement functions, such as fingerprint collecting, printing, and ID or fingerprint identification.
- This permission is available only to PC/2-in-1 device applications.
Applications do not need to use this permission in other scenarios.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: system_basic
Authorization mode: system_grant
Since: 11
ohos.permission.ACCESS_DDK_HID
Allows extended peripheral drivers to access the HID DDK interfaces to implement development of HID extended peripheral drivers.
Applicable scenarios and functionalities:
- The application needs to access a HID device, such as a handwriting tablet, game controller, keyboard & mouse device.
- This permission is available only to PC/2-in-1 device applications.
Applications do not need to use this permission in other scenarios.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: system_basic
Authorization mode: system_grant
Since: 11
ohos.permission.READ_PASTEBOARD
Allows an application to read Pasteboard data.
Applicable scenarios and functionalities:
-
This permission is available to PC/2-in-1 device applications.
- By default, the system grants this permission for PC/2-in-1 device applications. However, users can change the permission settings on the Settings > Privacy & Security page.
- On the Settings page of PCs/2-in-1 devices, users can choose between two options: Allow and Deny. Other devices offer three options: Always allow, Ask each time, and Deny.
-
The applications on other devices can request this permission only in the following scenarios:
- Bank applications need to read bank card numbers from Pasteboard to automatically generate cards.
- The application needs to read the password in a specific format from Pasteboard and automatically open the corresponding page in the application.
- Document editing application.
- The system-level input method needs to read Pasteboard information to implement automatic filling. This permission is not available for the application's built-in input method.
- If an open-source framework is used in an application, this permission can be applied for because the paste control cannot be used.
An example is the application running on a phone.
- When a user copies a bank card number to the pasteboard, the user opens the banking application. The application needs to read the pasteboard and check whether the copied content is the bank card number. If yes, the application will prompt the user to perform operations such as bank transfer.
- After the user opens the application, the application needs to read the data from the pasteboard, check whether the data is the specific password data in the application, and automatically open the related page.
- As a typical document editing application, this application needs to be used on phones to edit documents.
- As a system-level input method application, this application needs to read the data (such as verification code) from the pasteboard to implement the autofill function.
Alternative for other scenarios: Use PasteButton to read Pasteboard data. For details, see Using PasteButton.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: user_grant
Supported devices: Phone | TV | Wearable | PC/2in1 | Tablet | Car
Since: 11
ohos.permission.FILE_ACCESS_PERSIST
Allows an application to support persistent access to file URIs.
In API version 12, the permission level of this permission is changed to normal.
- If the application is only for local debugging:
- For versions before API version 12, you still need to use this permission by following the restricted permission application method.
- For API version 12 and later only, you can directly declare the permission.
-
If the application needs to be released to an application market:
You still need to use this permission by following the restricted permission application method.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: normal
Authorization mode: system_grant
Since: 11
Changelog: The permission level is system_basic in API version 11, and is changed to normal since API version 12.
ohos.permission.INTERCEPT_INPUT_EVENT
Allows an application to intercept input events.
Applicable scenarios and functionalities:
- The application is a cloud desktop or remote login client, which needs to display the cloud computer of the remote server or the screen of the remote computer on a local device.
- This permission is available only to PC/2-in-1 device applications.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: general devices
Since: 11
Changelog: The permission level is system_core in API version 11, and is changed to system_basic since API version 12. Since API version 26.0.0, this permission is available on all devices.
ohos.permission.INPUT_MONITORING
Allows an application to listen for input events.
Applicable scenarios and functionalities:
- The application needs to record the on-screen information, and keyboard key events or the mouse pointer effect or touch effect need to be displayed during the screen recording process.
- The application needs to share the screen.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 7
Changelog: The permission level is system_core in API versions 7 to 11, and is changed to system_basic since API version 12.
ohos.permission.SHORT_TERM_WRITE_IMAGEVIDEO
Allows an application to save images and videos to the user public directory within
up to 30 minutes after obtaining the permission. If it exceeds 30 minutes, a dialog box will be displayed again to request user authorization.
Applicable scenarios and functionalities:
- The application, such as an HTML5 web page app, cannot use SaveButton.
- Multiple images/videos cannot be saved at once in a save confirmation dialog.
Alternative for other scenarios: Use the security control or authorization dialog box to save the media resources specified by the user to the gallery. For details, see Saving Media Assets.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 12
ohos.permission.READ_WRITE_USER_FILE
Allows an application to access and modify files in user directories.
Applicable scenarios and functionalities:
- The IDE or debugging tool needs to read and write the user directory on the PC/2-in-1 device, for example, creating symbolic links or managing files in the user directory through a command-line tool.
- This permission is available only to PC/2-in-1 device applications.
Permission level: system_basic
Authorization mode: system_grant
Since: 13
ohos.permission.READ_WRITE_USB_DEV
Allows an application to connect to a device and read and write the device data via USB for debugging purposes.
Applicable scenarios and functionalities:
- The IDE or debugging tool needs to connect to a HarmonyOS device for development and debugging, for example, viewing the application logs on the device and performing profiling.
- This permission is available only to PC/2-in-1 device applications.
Permission level: system_basic
Authorization mode: system_grant
Since: 13
ohos.permission.GET_WIFI_PEERS_MAC
Allows an application to obtain the MAC address of the peer Wi-Fi device.
This permission is required if you want to obtain the MAC address of the peer device when obtaining the Wi-Fi scanning result.
Applicable scenarios and functionalities:
The IoT smart devices such as smart home devices and smart wearables need to connect to the network.
Permission level: system_basic
Authorization mode: system_grant
Since: 8
Changelog: The permission level is system_core in API versions 8 to 13, and is changed to system_basic since API version 14. It is available to normal applications.
ohos.permission.SET_TELEPHONY_ESIM_STATE_OPEN
Allows a carrier application to add eSIM configuration files.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 13
Changelog: The permission level is normal in API versions 13 and system_basic since API version 14.
ohos.permission.kernel.DISABLE_CODE_MEMORY_PROTECTION
Allows an application to disable its runtime code integrity protection.
Applicable scenarios and functionalities:
- The application needs to modify the instruction content at runtime.
- This permission is available only to applications on tablets, PCs, and 2-in-1 devices.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 14
ohos.permission.kernel.ALLOW_WRITABLE_CODE_MEMORY
Allows an application to apply for writable and executable anonymous memory. This capability is mainly used to provide just-in-time (JIT) compilation for the engines bundled with the application (such as JS engines and game script engines) to improve code execution efficiency.
Applicable scenarios and functionalities:
- The just-in-time (JIT) compilation of the application's built-in engine is enabled. This permission cannot be used for hot updates.
- Applications requesting this permission must adapt to the Secure Shield mode, ensuring no crashes occur in this mode.
- This permission is available only to applications on tablets, PCs, and 2-in-1 devices.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PC/2in1 | Tablet
Since: 14
ohos.permission.kernel.ALLOW_EXECUTABLE_FORT_MEMORY
Allows an application to have its system JS engine to apply for anonymous executable memory with the MAP_FORT identifier.
After the application obtains this permission, the system engine can apply for anonymous executable memory with the MAP_FORT identifier for just-in-time compilation, improving runtime execution efficiency.
Applicable scenarios and functionalities:
The game applications need to use the system engine to efficiently parse the game script.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 14
ohos.permission.ACCESS_DISK_PHY_INFO
Allows an application to obtain the disk hardware information.
Applicable scenarios and functionalities:
This permission is available only to securities applications for securities and stock trading.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 15
ohos.permission.PRELOAD_FILE
Allows an application to preload files to improve the file opening speed.
Applicable scenarios and functionalities:
This permission is available only to document editing applications.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices | tablets
Since: 15
Changelog: Since API version 26.0.0, this permission is also available on tablets.
ohos.permission.SET_PAC_URL
Allows an application to set the URL of the proxy auto config (PAC) script.
After the script address is configured, other applications can read and parse this script and determine whether to use a proxy based on the parsing result.
Applicable scenarios and functionalities:
- Enterprise applications need to set an intranet proxy to manage enterprise traffic.
- Government and public service applications and their trusted enterprise applications in China need to set a proxy to access secure websites.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 15
ohos.permission.PERSONAL_MANAGE_RESTRICTIONS
Allows a device administrator application to manage personal device restrictions.
Applicable scenarios and functionalities:
This permission is available only to user as developer (UAD) applications.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 15
ohos.permission.START_PROVISIONING_MESSAGE
Allows an application to start the device management service deployment process, which activates the application as a personal device administrator application.
Applicable scenarios and functionalities:
This permission is available only to user as developer (UAD) applications.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 15
ohos.permission.USE_FRAUD_CALL_LOG_PICKER
Allows an application to use the fraud call log Picker to obtain call logs.
Applicable scenarios and functionalities:
It is available only to anti-fraud apps.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 15
ohos.permission.USE_FRAUD_MESSAGES_PICKER
Allows an application to use the fraud message Picker to obtain SMS messages.
Applicable scenarios and functionalities:
It is available only to anti-fraud apps.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 15
ohos.permission.PERSISTENT_BLUETOOTH_PEERS_MAC
Allows an application to persist the virtual address corresponding to the MAC address of the peer Bluetooth device.
With this permission and the access.addPersistentDeviceId method, the application can persist the virtual address of the peer Bluetooth device obtained via BLE scanning, BR scanning, or listening for connections. The persistent virtual address can still be used even if Bluetooth is enabled or disabled, or the Bluetooth device is restarted.
Applicable scenarios and functionalities:
The application needs to connect to devices, such as smart home devices, smart wearables, and smart travel devices, through Bluetooth scanning to bind the user devices, and display device status or control devices.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 16
ohos.permission.ACCESS_VIRTUAL_SCREEN
Allows an application to manage virtual screens.
With this permission, the application can call APIs to perform virtual screen management, including creating, using, and destroying a virtual screen.
Applicable scenarios and functionalities:
The application needs to connect to a telematics device to play videos or use map navigation.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 16
ohos.permission.MANAGE_APN_SETTING
Allows an application to read or set APN information.
Applicable scenarios and functionalities:
The application needs to connect to the mobile data private network for office tasks.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 16
ohos.permission.GET_WIFI_LOCAL_MAC
Allows an application to obtain the MAC address of the local Wi-Fi device.
Applicable scenarios and functionalities:
- Securities trading, such as stock, futures, and bond trading Applicable devices: PCs and 2-in-1 devices.
- Online banking transaction or identity authentication: online banking services (such as account query, transfer, and remittance), or identity authentication, signing, and signature verification tools for online banking users Applicable devices: PCs and 2-in-1 devices.
- Video applications. Applicable devices: TVs.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 8
Changelog: For API versions 8 to 15, this permission is available only to system applications. For API versions 16 and later, this permission is available to normal applications on PCs/2-in-1 devices, and is available only to system applications on other devices.
ohos.permission.kernel.ALLOW_USE_JITFORT_INTERFACE
Allows an application to call the JITFort API to update the content in MAP_FORT.
Applicable scenarios and functionalities:
The application uses its own script engine and has JIT compilation enabled.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 16
ohos.permission.GET_ETHERNET_LOCAL_MAC
Allows an application to obtain the current MAC address of the Ethernet.
Applicable scenarios and functionalities:
- Securities trading, such as stock, futures, and bond trading Applicable devices: PCs and 2-in-1 devices.
- Online banking transaction or identity authentication: online banking services (such as account query, transfer, and remittance), or identity authentication, signing, and signature verification tools for online banking users Applicable devices: PCs and 2-in-1 devices.
- Video applications. Applicable devices: TVs.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 13
Changelog: In API 13, this permission is open only to MDM applications. Starting from API 14, the open scope is changed from MDM applications to normal enterprise applications. Starting from API 16, it is open to normal applications on PCs/2-in-1 devices, while on other devices it remains open only to system applications.
ohos.permission.kernel.DISABLE_GOTPLT_RO_PROTECTION
Allows an application to disable the read-only protection on .got.plt.
Applicable scenarios and functionalities:
The basic capabilities required by the application functionality are not supported by the system currently and must be implemented by modifying .got.plt. When requesting this permission, you must state the reason why the system does not meet the requirements.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 17
ohos.permission.USE_FRAUD_APP_PICKER
Allows an application to use the fraud app Picker to obtain application information.
Applicable scenarios and functionalities:
It is available only to anti-fraud apps.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Since: 18
ohos.permission.ACCESS_DDK_DRIVERS
Allows an extended peripheral driver client to bind to the driver server.
This permission can be requested successfully only when:
- The target extension driver server in the value field of the permission declaration for the extended peripheral driver client has been launched or both the server and client have been launched.
- The capabilities provided by the target extension driver server comply with the requirements of the extended peripheral driver client.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: system_basic
Authorization mode: system_grant
Extra data: Yes. For details about the configuration method, see UI-based Driver Development.
Since: 18
ohos.permission.ACCESS_DDK_SCSI_PERIPHERAL
Allows an extended peripheral driver to access the SCSI DDK APIs to implement development of SCSI extended peripheral drivers.
The APIs can be used to develop the following types of extended peripheral drivers:
Peripherals connected to the host via a USB bus and:
- InterfaceClass of the peripheral is Mass Storage (0x08) and InterfaceSubClass is SCSI Transparent Command Set (0x06).
- The peripheral can simulate a SCSI device in a way that is transparent to the operating system.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: system_basic
Authorization mode: system_grant
Since: 18
ohos.permission.ACCESS_DDK_USB_SERIAL
Allows an extended peripheral driver to access the USB Serial DDK APIs.
The USB Serial DDK APIs can be used to develop the following types of extended peripheral drivers:
Peripherals connected to the host via a USB bus and:
- InterfaceClass of the peripheral is Communication Device Control Class (0x02) and InterfaceSubClass follows ACMSubClass model(0x02).
- The peripheral can simulate traditional serial communication through a USB interface.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices | tablets
Since: 18
ohos.permission.CUSTOM_SANDBOX
Allows an application to set the sandbox type to dynamic sandbox.
Applicable scenarios and functionalities:
The application is a development tool (such as DevEco Studio, DevEco Testing, or CLI) running on a PC or 2-in-1 device. It is used to develop, debug, and test other applications.
Permission level: system_basic
Authorization mode: system_grant
Since: 18
ohos.permission.atomicService.MANAGE_STORAGE
Allows a mini game of the atomic service type to manage its storage space.
Applicable scenarios and functionalities:
This permission can be requested if the storage space size needs to be adjusted for mini games of the atomic service type.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 20
ohos.permission.MANAGE_SCREEN_TIME_GUARD
Allows an application to call the screen time guard APIs to restrict screen usage, apply application access control, and control the screen usage time.
Applicable scenarios and functionalities:
- Personal usage management: allowing users to monitor and control their own device and application usage, with the option to limit access to applications or screen time as needed for the purpose of focus, habit-building, and self-discipline
- Supervised usage management: enabling schools, parents, or organizations to oversee and manage the device and application usage of students, children, or employees, with the option to limit access to applications or screen time as needed for the purpose of protection, guardianship, and care
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | tablets
Since: 20
ohos.permission.CUSTOMIZE_SAVE_BUTTON
Allows an application to customize the icon and text of SaveButton.
Applicable scenarios and functionalities:
The default style provided by the saving control cannot meet business scenarios. The application needs to customize the icon and text of the saving control.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: general devices
Since: 20
ohos.permission.GET_ABILITY_INFO
Allows an application to query Ability information based on the URI or FileType.
Applicable scenarios and functionalities:
Currently, only browser applications on PCs and 2-in-1 devices can request this permission.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 20
ohos.permission.ACCESS_FIDO2_ONLINEAUTH
Allows an application to use the Native Development Kit (NDK) of the passkey service.
Applicable scenarios and functionalities:
The application needs to use the passkey service to implement password-free authentication on web pages.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 20
ohos.permission.USE_FLOAT_BALL
Allows an application to use the global floating ball.
With this permission, an application can implement cross-application interaction and directly access services to handle user tasks.
Application conditions
- The application must provide an independent switch for enabling the global floating ball. The switch must be disabled by default and can be enabled only by users.
- The content and functions displayed in the floating ball must match the actual functions in the application.
- The content displayed in the floating ball cannot be used for marketing, advertising, or payment guidance.
Applicable scenarios and functionalities:
The following scenarios are required:
- Question search
- Billing record
- Product price comparison
- Order grabbing
- Translation
- Real-time monitoring of financial applications
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 20
Changelog: Since API version 26.0.0, this permission is also available on PCs/2-in-1 devices.
ohos.permission.AUTO_RESTORE_MAIN_WINDOW
Allows an application to automatically restore its main window through the global floating ball.
Prerequisites: This permission can only be requested together with the ohos.permission.USE_FLOAT_BALL permission.
Applicable scenarios and functionalities:
For professionals such as drivers, food delivery driver, and delivery personnel using vocational applications for order-grabbing, the applications can use the floating ball to automatically restore the main window and load specific pages, assisting these users in efficient order-grabbing.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | tablets
Since: 24
ohos.permission.DLP_GET_HIDE_STATUS
Allows an application to use the information hiding APIs to obtain the information hiding status.
With this permission, the application can obtain the current screen peeping state, that is, whether the screen is being peeped by others.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones
Since: 18
Changelog: This permission is available only to system applications in API versions 18 to 19. From API version 20, it's also available to normal applications.
ohos.permission.READ_LOCAL_DEVICE_NAME
Allows an application to obtain the local device name.
With this permission, the application can obtain the device name on the About screen in Settings. Without this permission, the application can only obtain the default device name.
Applicable scenarios and functionalities:
This permission is available only when the application needs to display the login device name during cross-device login via QR code scanning.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 20
ohos.permission.KEEP_BACKGROUND_RUNNING_SYSTEM
Allows an application to request continuous tasks of special types, such as computing tasks.
Applicable scenarios and functionalities:
Automatic order receiving for merchant applications.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: general devices
Since: 20
ohos.permission.LINKTURBO
Allows an application to achieve multipath transmission.
With this permission, the application can initiate operations such as multi-network activation, monitoring, and release for multipath transmission.
Applicable scenarios and functionalities:
- Multi-network traffic steering or redundant transmission in weak network environments for audio and video calls and conferences, games, online education, short and long videos, and live streaming, enhancing network anti-jitter performance and transmission reliability
- Transmission via multiple IP addresses when both the application and server support multi-network concurrency
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 20
ohos.permission.ACCESS_NET_TRACE_INFO
Allows an application to detect the network and obtain the TraceRoute information to determine the possible causes of high network latency.
Applicable scenarios and functionalities:
Detecting network link quality or faults in network-based scenarios such as audio/video calls and conferences, games, online education, and live broadcasts that are sensitive to network latency.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: general devices
Since: 20
ohos.permission.READ_WHOLE_CALENDAR
Allows an application to read all calendar information.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: system_basic
Authorization mode: user_grant
Since: 9
Changelog: This permission is available only to system applications in API versions 9 to 19. From API version 20, it's also available to normal applications.
ohos.permission.WRITE_WHOLE_CALENDAR
Allows an application to add, remove, or change all calendar events.
Review time after the request is submitted: The request will be approved immediately after being submitted.
Permission level: system_basic
Authorization mode: user_grant
Since: 9
Changelog: This permission is available only to system applications in API versions 9 to 19. From API version 20, it's also available to normal applications.
ohos.permission.HOOK_KEY_EVENT
Allows an application to intercept key events.
With this permission, the application can integrate its custom key handling process into the system's key handling process prior to the key event being dispatched to the application window.
Applicable scenarios and functionalities:
-
- Securities login or trading, such as stock, futures, and bond trading
-
- Online banking transaction or identity authentication: online banking services (such as online banking login, transfer, and remittance), or password control tools for identity authentication for online banking users
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: manual_settings
Supported devices: PCs/2-in-1 devices | tablets
Since: 21
ohos.permission.WEB_NATIVE_MESSAGING
Allows an application to use the web native messaging capability.
With this permission, the application can enable communication between browser extensions and local applications.
Applicable scenarios and functionalities:
Browser-type applications where users need to access web pages and browse Internet resources by entering URLs
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 21
Changelog: Since API version 24, this permission is also available on mobile phones and tablets.
ohos.permission.SUBSCRIBE_NOTIFICATION
Allows an application to read notifications published by the system or installed applications.
Applicable scenarios and functionalities:
Wearable applications used by smart watches that can display notifications
With this permission, the application can read notifications published by the system or installed applications, and then forward these notifications to the corresponding watch through short-range communication protocols such as Bluetooth to display the notifications.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | tablets
Since: 22
ohos.permission.CUSTOM_SCREEN_RECORDING
Allows an application to record the screen without displaying any pop-up.
With this permission, the application can record the screen without showing a privacy pop-up each time recording is initiated.
Applicable scenarios and functionalities:
- Applications that support screen recording triggered via a UI component
- Applications that support remote login and can display the remote login screen on a local device
- Applications that support desktop sharing and can share the local device's screen with other devices
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: manual_settings
Supported devices: PCs/2-in-1 devices | TVs
Since: 22
Changelog: Since API version 26.0.0, this permission is also available on TVs.
ohos.permission.ALLOW_EXTERNAL_NATIVE_CODE
Allows an application to use external native programs.
With this permission, the application can load external dynamic link libraries (.so), binary files (.bin), etc.
Applicable scenarios and functionalities:
Tool applications running on PCs/2-in-1 devices, such as IDEs and command line tools
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 23
ohos.permission.GET_IP_MAC_INFO
Allows an application to obtain the IP address and MAC address of a network device.
Applicable scenarios and functionalities:
The application obtains the IP address and MAC address of a network device for Internet connection or identification, and cannot be used for device positioning.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: general devices
Since: 22
ohos.permission.atomicService.MANAGE_AGING
Allows an atomic service to request differentiated aging policies.
Applicable scenarios and functionalities:
This permission can be requested when a HarmonyOS mini game needs to delay aging. For example, if the HarmonyOS mini game is a standalone game, its data needs to be cached locally.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 23
ohos.permission.ACCESS_USER_FULL_DISK
Allows an application to access the user public directory without a dialog.
With this permission, the application can access the public directory without having to notify the user via a pop-up every time.
Applicable scenarios and functionalities:
- Remote login client applications: display of the remote device screen on a local device
- Antivirus applications: full-disk virus scan and removal
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: manual_settings
Supported devices: PCs/2-in-1 devices
Since: 22
ohos.permission.kernel.LOAD_INDEPENDENT_LIBRARY
Allows an application to load shared libraries signed with binary certificates.
Applicable scenarios and functionalities:
This permission is open to Huawei ecosystem development tool applications.
Risk description: This permission allows the loading of unreviewed code, which may affect the application security. Therefore, exercise caution when using this permission.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 20
Changelog: This permission is available only to system applications in API versions 20 to 21. From API version 22, it's also available to normal applications.
ohos.permission.CRYPTO_EXTENSION_REGISTER
Allows an application to register and unregister the crypto extension.
Applicable scenarios and functionalities:
- UKey developers
- Banking and financial applications with UKey vendor collaboration certification
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices | tablets | phones
Since: 22
Changelog: This permission is also available on tablets since API version 24 and on mobile phones since API version 26.0.0.
ohos.permission.MANAGE_MEDIA_RESOURCES_FOR_PUBLIC
Allows an application to obtain and manage the media resources playing on a device.
Applicable scenarios and functionalities:
controller applications for devices such as smart watches and IoT devices
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets | TVs | cars
Since: 23
ohos.permission.MANAGE_RECENT_SNAPSHOT
Allows an application to set the preview image displayed when a mouse hovers over its icon in the Dock or recent tasks are viewed.
When the mouse hovers over an application icon in the Dock or recent tasks are viewed, a real-time preview image of the application will be displayed. With this permission, the application is authorized to customize this image.
Applicable scenarios and functionalities:
VM applications
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.SET_WINDOW_ALPHA
Allows an application to set the main window container to be transparent.
With this permission, the application can set the background color of the main window container.
Applicable scenarios and functionalities:
VM applications
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.MANAGE_CALL_FOR_DEVICES
Allows an application to manage the call state, such as obtaining the incoming call number, answering, rejecting, and hanging up calls.
Applicable scenarios and functionalities:
- The HAP that applies for this permission is the application for a third-party wearable device.
- The HAP application has a specific application scenario where the call status needs to be obtained and the call control is required.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 23
ohos.permission.SET_WINDOW_TOUCH_AREAS
Allows an application to configure a touch target for window events. Events occurring outside the touch target will be passed through.
Applicable scenarios and functionalities:
VM-related app vendors
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.MANAGE_BLUETOOTH_ADVERTISER_NAME
Allows an application to customize the BLE broadcast name.
Applicable scenarios and functionalities:
An application needs to send a BLE broadcast with a custom name to communicate with nearby devices.
Example:
An application sends a BLE broadcast with a custom name. Nearby devices detect this broadcast, recognize the device by its name, and send a connection request.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: general devices
Since: 23
ohos.permission.INPUT_DEVICE_CONFIGURATOR
Allows an application to bind input devices to displays.
With this permission, the driver application can bind external input devices connected via USB or Bluetooth with specific display screens.
Applicable scenarios and functionalities:
On PCs or 2-in-1 devices connected to multiple displays, when a user operates an input device, the driver application maps the user's interaction targets to a specific display.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 24
ohos.permission.REGISTER_OBJECTEDITOR_EXTENSION
Allows an application to register ObjectEditorExtensionAbility components.
With this permission, the application can provide embedded content editing services for use by other applications.
Applicable scenarios and functionalities:
This permission is granted only to document editing apps and apps that provide specific document fragment editing capabilities for document editing apps (such as formula editors).
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 24
ohos.permission.ALLOW_ACCESSORY_ACCESS
Allow an application to use the accessory connection service for pairing and auto-wake functions.
Applicable scenarios and functionalities:
Applications requiring seamless collaboration between trusted accessories and a device
Example:
- When an accessory initiates a file transfer request to a device, the accessory connection service receives the request and wakes up relevant applications and services in the background.
- During a video call or live stream on a device, the accessory connection service detects nearby accessories and wakes up the distributed camera service to facilitate the use of the accessory's camera.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets | cars
Since: 26.0.0
ohos.permission.CHECK_CALL_LOG
Allows an application to query the system for matching call records within a specified period based on specific criteria (such as the mobile number and call duration).
Applicable scenarios and functionalities:
Vocational applications used by professionals such as drivers, food delivery drivers, and delivery personnel Applications that need to verify whether a valid call record exists between a specific number and the user within a specified period
Example:
When a delivery person places a package in a locker or leaves it with a security guard, the application needs to check whether this person has successfully contacted the recipient via phone.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: general devices
Since: 24
ohos.permission.GET_NETWORK_STATS
Allows an application to query the traffic data of other applications.
Applicable scenarios and functionalities:
- VPN applications, which are used to query related traffic consumption.
- Traffic management applications, which are used to collect traffic statistics.
- MDM application
- System application
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: general devices
Since: 10
Changelog: Enable via ACL is false for this permission in API versions 10 to 11, and is changed to true since API version 12. For API versions 10 to 24, this permission is available to system applications. Since API version 26.0.0, this permission is available to normal applications.
ohos.permission.ACCESS_DLP_SERVICE
Allows an application or a service to use the DLP to register or unregister the plugin for connecting the server.
Applicable scenarios and functionalities:
Allows an application to use the DLP to register or unregister the plugin for connecting the server.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets | TVs
Since: 26.0.0
ohos.permission.CONTROL_DEVICE
Allows an application to inject input events to control the device.
Applicable scenarios and functionalities:
Required when the controlled end of the remote login device needs to receive input events from the controlling end to operate the local device.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: manual_settings
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.KEEP_BACKGROUND_RUNNING_SPECIAL_SCENARIO
Allows an application to apply for a continuous task of the special type.
Applicable scenarios and functionalities:
The application needs to keep alive in the background in special scenarios.
Example:
- The application exports media files in the background.
- The application uses a third-party casting component to cast content in the background.
- The application has indoor workout scenarios in the background.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 24
ohos.permission.FLOAT_VIEW
Allows an application to use floating windows.
Applicable scenarios and functionalities:
The application must support the cross-application floating window for displaying critical information. Currently, this is only open to game streaming in live broadcast applications and real-time market tracking in financial applications. Example:
- Game streaming: After a streamer enables the floating window function in a live broadcast application, a floating window will display interactive content from the chatroom when the application is running in the background. This allows the streamer to view live updates in real-time and quickly adjust broadcast settings.
- Financial market tracking: After a user enables the market-tracking floating window function in a financial application, a floating window will provide real-time updates on market data even when the application is in the background, allowing the user to stay informed of market dynamics at any time.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: user_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 26.0.0
ohos.permission.GET_CALL_TRANSFER_INFO
Allows an application to query the call forwarding status.
Applicable scenarios and functionalities:
- The application is a mobile banking application.
- In addition, the application must contain the bank transfer service for risk assessment before bank transfer.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 26.0.0
ohos.permission.MANAGE_SKILL
Allows an application to use Skills.
With this permission, the application can:
- Query information about skill packages.
- Listen for events such as the installation, update, and uninstallation of skill packages.
- Access the sandbox directory where skill packages are installed.
Applicable scenarios and functionalities:
The application must be an AI Agent application.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.kernel.AS_LDK_DRIVER
Allows an application to install the PCIe driver.
Applicable scenarios and functionalities:
This permission is available only to driver developers of PCIe device vendors.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.ACCESS_GAME_BUDDY_SERVICE
Allows an application to access the game companion service.
After obtaining this permission, the application can use the APIs provided by the game companion service, such as obtaining screenshots of running game applications and obtaining the foreground/background status of game applications.
Applicable scenarios and functionalities:
The application provides game AI companion features, requiring the analysis of game screenshots while a user is playing to deliver in-game advice and recommendations.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: Phone | PC/2in1 | Tablet | TV
Since: 26.0.0
Change information: Starting from API version 26.0.0, support is added for applying on tablets, PCs/2-in-1 devices, and TVs.
ohos.permission.KNOCK_COLLABORATION
Allows an application to connect to a specific device using Tap-to-Transfer for information exchange and cross-device interaction.
Applicable scenarios and functionalities:
Applicable scenarios and functionalities:
-
The application needs to transfer data between devices, such as HAP packages, resource packages, or specific in-application data types.
Example: When a user opens the application on device A and taps device B where the application is not installed, the HAP package can be transferred from device A to device B and automatically installed.
-
The application needs to launch its counterpart on another device.
Example: When a user opens the application on device A and taps device B where the application is already installed, the corresponding page will be launched on device B.
-
The application needs to enable real-time interaction between devices via Tap-to-Transfer.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones
Since: 26.0.0
ohos.permission.PRINTER_DRIVER
Allows an application to manage the printing system.
Applicable scenarios and functionalities:
Printer driver applications that need to add custom printers, delete printers, and perform other management tasks Example:
- When the printer driver application is opened for the first time, a specific printer is added.
- The printer driver application needs to delete all printers of the same brand in one click.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices | phones | tablets
Since: 24
ohos.permission.kernel.SUPPORT_LOCAL_PLUGIN
Allows an application to install and load self-distributed plug-ins.
Self-distributed plug-ins are not released on AppGallery and are distributed by the application itself. This permission allows the loading of unverified code. Exercise caution when using this permission.
Applicable scenarios and functionalities:
The application has an extension plug-in that involves ArkTS code calling.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.MANAGE_AUDIO_ACCESSORY
Allows an application to register audio accessories with the system.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: Phone | TV | PC/2in1 | Tablet | Car
Since: 26.0.0
ohos.permission.ALLOW_USE_BM
Allows an application to call BM tools in developer mode.
Applicable scenarios and functionalities:
Only shell applications and Integrated Development Environment (IDE) applications running on PCs or 2-in-1 devices can request this permission.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.ACCESS_DIGITAL_IDENTITY
Allows an application to import digital credentials using the digital identity service.
With this permission, the application can import the user's digital identity credentials into the device for secure storage and convenient presentation afterward.
Applicable scenarios and functionalities:
- This permission is exclusively open to qualified enterprise developers and currently unavailable to individual developers.
- The application must be qualified to issue digital credentials to users. The applicant must be a credential issuing authority or authorized by at least one credential issuing authority to import authentic digital credentials for users before applying for this permission.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | tablets
Since: 26.0.0
ohos.permission.CAPTURE_PLAYBACK_DOWNLINK
Allows an application to record downlink data of cellular calls.
Applicable scenarios and functionalities:
This permission can be requested for specialized scenarios targeting workers with disabilities, as well as applications involved in the workflows of drivers, food delivery personnel, and couriers.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | tablets
Since: 26.0.0
ohos.permission.MANAGE_SANDBOX_BUNDLE
Allows an application to manage sandbox applications.
Applicable scenarios and functionalities:
This permission applies only to AI agent applications.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: PCs/2-in-1 devices
Since: 26.0.0
ohos.permission.DETECT_DEVICE
Allows an application to invoke the smart diagnosis service to obtain data.
Applicable scenarios and functionalities:
The application must possess qualifications for recycling second-hand electronic devices and have signed the Data Sharing Agreement (DSA). This permission can be requested when engaging in the second-hand electronic device recycling service.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | PCs/2-in-1 devices | tablets
Since: 26.0.0
ohos.permission.ACCESS_SE_KEY
Allows an application to generate, use, and delete secure element keys.
Applicable scenarios and functionalities:
- This permission is restricted to digital shield–related scenarios, including high‑security scenarios (e.g., transfers, payments, and digital signatures) in financial and enterprise applications. These applications must have open digital shield capabilities.
- This permission involves SE keys management capabilities and relies on hardware support. Ensure that the target device supports the required functions.
Review time after the application is submitted to AppGallery Connect: The review result will be provided within three working days.
Permission level: system_basic
Authorization mode: system_grant
Supported devices: phones | wearables | TVs | PCs/2-in-1 devices | tablets | cars
Since: 26.0.0