From d8e1354fe182b2d27cf5f72b8cec52db528d0b53 Mon Sep 17 00:00:00 2001 From: liyan Date: Thu, 2 Feb 2023 03:01:18 +0000 Subject: [PATCH] update en/application-dev/security/accesstoken-guidelines.md. Signed-off-by: li-yan339 Signed-off-by: liyan --- en/application-dev/security/accesstoken-guidelines.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/en/application-dev/security/accesstoken-guidelines.md b/en/application-dev/security/accesstoken-guidelines.md index 3bcced1762..227c30112e 100644 --- a/en/application-dev/security/accesstoken-guidelines.md +++ b/en/application-dev/security/accesstoken-guidelines.md @@ -117,7 +117,8 @@ For example, if an application needs to access audio files of a user and capture ## Requesting User Authorization If an application needs to access user privacy information or use system abilities, for example, accessing location or calendar information or using the camera to take photos or record videos, it must request the permission from users. A permission verification is performed first to determine whether the current invoker has the corresponding permission. If the application has not obtained that permission, a dialog box will be displayed to request user authorization. The following figure shows an example. - + +![](figures/permission-read_calendar.png) > **NOTE**
Each time before an API protected by a permission is accessed, [**requestPermissionsFromUser()**](../reference/apis/js-apis-abilityAccessCtrl.md#requestpermissionsfromuser9) will be called to request user authorization. After a permission is dynamically granted, the user may revoke the permission. Therefore, the previously granted authorization status cannot be persistent. -- GitLab