In Detailed Explanation of Permission Features, it is explained that different permissions can only be obtained through authorization by the permission owner. Starting from V2.48 version of the DataWind product, approval workflows through Lark are supported, allowing users to independently apply for permissions from resource owners. Once the owner approves, the applicant will obtain the corresponding permissions for the requested resource. This reduces the threshold for data usage and shortens the time required for data or IT personnel to grant data permissions.

(1) Go to the Lark Open Platform, enter the backend of the bot that needs to push configuration messages, and click Event Subscription

(2) Click Request Address Configuration and fill in the configuration information: http://environment address (ip:port or domain name)/aeolus/api/v3/dispatcher/action

(3) Select Add "Approval Instance Status Change" event, then enable the [Access Approval Application] permission


(4) According to Configure permission management the steps, add the following four permissions: [View, Create, Update, Delete Approval Application Related Information], [Query Approval List], [Access Approval Application], and [Get User user ID].

(5) After completing the above, click Application Release -- Version Management and Release, then click Create Version, and follow Publish the Lark application the steps to publish.

(6) After completing all the above operations, return to the DataWind platform, log in as an administrator, go to System Management Configuration, and click Approval Settings on the left to start the following configuration.

(7) Select process administrators

• Multiple process administrators can be selected, but only users who have completed Lark account binding on the platform can be selected.
• The process administrator serves as a fallback. The configured Larkrk process will first send approval to the resource administrator of the resource. However, if none of the resource administrators have bound their Lark accounts, the approval will be routed to the process administrator.

(8) After completing the above operations, set the status to enabled to complete the configuration of the Lark approval workflow

3.1 Initiate permission approval #

When there are cases where dashboard permissions, chart permissions, data permissions, project permissions, and so on are not visible, click Apply for Permission to initiate an approval process.

Caution: Currently, visual modeling, large screens, and data connections do not support integration with the Lark approval workflow.

• Dashboard: If you do not have resource-level permissions such as view or edit, the following prompt will appear.
• You have dashboard permissions, but do not have data row or column permissions.
• No permissions for datasets or dataset folders, and so on.
• No permissions for project spaces.

3.2 Fill in the approval application #

• The configured Lark process will first send approval to the resource administrator of the resource. However, if none of the resource administrators have bound their Lark accounts, the approval will be routed to the process administrator.
• When a user clicks to apply for permission without having the required permissions, the interface will redirect as shown below. The user can apply for permissions for the resource, or add other resource permissions to combine into a single application; for explanations of resource permissions Authorization Operations Manual.
• After clicking Submit, the effect shown in the illustration will appear. Click the [Approval] link in the upper right corner to quickly jump to the workspace to view the approval workflow.

3.3 Approval process notifications #

• After clicking Apply, both the applicant and the approver will receive a message notification.
  • Applicant
  • Approver
• After receiving the notification, the approver can choose to approve or reject the application.
  • Approve application
  • Reject application
• After the approver takes action, the applicant will also receive a notification indicating whether the application was approved or rejected.
  • If the application is approved, the applicant can view the resource in DataWind and use it within the scope of the approved permissions.
  • If the application is not approved, the applicant will remain without permissions for the resource as before.