Approval settings

更新时间:
复制 MD 格式

After you enable the approval flow, an organization administrator can configure whether to provide an entry point for users to request permissions on data works. The administrator can also configure the approval channel and default approvers.

Limitations

Approval settings are available only in Quick BI Enterprise Standard.

Entry point

Log on to the Quick BI console as a permission administrator and follow the instructions in the figure below to enable the organization-level setting for permission requests.

Authorization settings

On the Collaborative Authorization Settings tab, in the Approval Settings section, you can Enable Approval Flow and configure the following parameters.

Parameter

Description

Basic Settings

Controls whether to show an entry point for users to request permissions on data works in all workspaces in the organization.

  • Enable Approval Flow: Enables or disables the approval flow for your organization.

  • Application Settings:

    • Data Works Page Application: If you select this option, unauthorized users can see an entry point to request permissions on the data works page.

      Note

      Data works include data portals, dashboards, workbooks, self-service data retrieval, ad hoc analysis, data visualization screens, data entry forms, and Q-reports.

    • Column-level Permission Application: If you select this option, unauthorized users can see an entry point to request permissions on a dataset.

      For more information, see Set up the request entry point.

  • Default Approver: Sets the default approver for the approval flow. Default approvers can include permission administrator, workspace administrator, owner of data works, and enterprise security administrator.

    You can select multiple default approvers.

    • If you select permission administrator, you can choose a permission administrator when you submit a permission request.

    • If you select workspace administrator, you can choose a workspace administrator when you submit a permission request. A workspace administrator can approve requests for all data works in their workspace, including data portals, dashboards, workbooks, self-service data retrieval, ad hoc analysis, data visualization screens, and data entry forms.

    • If you select owner of data works, permission requests for a specific item are sent to its owner by default.

    • If you select enterprise security administrator, you can choose an enterprise security administrator when you submit a permission request. An enterprise security administrator is a role with permissions for the Enterprise Security module in System Management.

      Note

      The term enterprise security administrator is not a specific role. It refers to any user with permissions for the Organization Management > Enterprise Security module, which covers centralized authorization, collaborative authorization settings, and data security. This includes organization administrators and permission administrators, who have these permissions by default, along with any users assigned to custom roles that grant these permissions.image

Approval Channel

Sets the channel for the permission approval flow. Available channels include approval within platform, custom approval channel, DingTalk, WeCom, and Lark.

  • Approval Within Platform: If you select this option, the approval flow notifies approvers through system messages within the Quick BI platform.

    image

    You can select either Allow in-platform approval or Notify only.

    • If you select Allow in-platform approval, approvals can be processed directly within the platform.

    • If you select Notify only, the platform displays approval notifications but does not allow direct actions on them. You can use this option with the custom DingTalk template feature to enable dynamic countersigning in DingTalk, where the in-platform notification serves only as a log record. For more information, see Handle permission applications.

  • Custom approval channel: If you select this option, the approval flow notifies approvers through your custom-configured channel.

  • DingTalk channel approval: If you select this option, approval requests are sent as application messages to approvers in DingTalk. For more information, see DingTalk channel approval.

  • WeCom channel approval: If you select this option, approval requests are sent as application messages to approvers in WeCom. For more information, see WeCom channel approval.

  • Lark channel approval: If you select this option, approval requests are sent as application messages to approvers in Lark. For more information, see Lark channel approval.

    After you configure the approval flow interface, users with linked accounts can initiate permission requests in Quick BI, which are then routed to the external system for approval.

Note
  • If you have authorized multiple enterprises in the Office Suite Integration section, you cannot enable the approval channel for the corresponding office suite. For example, if you have integrated multiple DingTalk enterprises, you cannot enable DingTalk channel approval.image

  • If an approval channel for DingTalk, WeCom, or Lark is already enabled, you cannot add multiple enterprise authorizations for that channel.

Configure request entry point

Request entry point settings include Data Works Page Application and Column-level Permission Application.

  • Data Works Page Application: Specifies whether to provide an entry point for requesting permissions on data works in all workspaces within the organization.

    • If you select Data Works Page Application, users can see an entry point to request permissions in the data works list.

      Data works include data portals, dashboards, workbooks, self-service data retrieval, ad hoc analysis, data visualization screens, data entry forms, and Q-reports. The following example uses a dashboard.

      Apply for edit permissions image.png Apply for view permissions image.png

    • If you do not select Data Works Page Application, users can only see the list of data works but cannot request permissions for them.

  • Column-level Permission Application: Controls whether to display an entry point to request view permissions for masked data.

    • If you select Column-level Permission Application, the line chart below shows an example of the result.image.png

    • If you do not select Column-level Permission Application, the line chart below shows an example of the result.image.png

Custom channel approval

After an organization administrator enables and configures the approval flow, permission requests initiated in Quick BI can be routed to an external system for approval.

  1. On the configuration management page, create a new custom channel as shown in the following figure.image.png

  2. On the collaborative configuration page, enable the custom approval channel as shown in the following figure.

    image.png

    Now, when a user requests permissions for a Quick BI resource, the custom channel also receives a request notification.

DingTalk channel approval

After an organization administrator enables the approval flow and selects the DingTalk channel, you can initiate permission requests in Quick BI that are sent to DingTalk for approval.

  1. If your organization has not yet bound a DingTalk micro-app or authorized DingTalk API access, go to the configuration page to complete these steps as shown in the figure. For detailed instructions, see DingTalk API authorization.

  2. If your organization has already bound a DingTalk micro-app, you can select the checkbox to enable DingTalk channel approval and then create an approval template.

    image

  3. After creating the template, you can test its content. Select a recipient and click Send Test.

    image

  4. Click Confirm to complete the channel configuration. You can then test and verify the setup.

    image

WeCom channel approval

After an organization administrator enables the approval flow and selects the WeCom channel, you can initiate permission requests in Quick BI that are sent to WeCom for approval.

  1. If your organization has not yet bound a WeCom micro-app or authorized WeCom API access, go to the configuration page to complete these steps as shown in the figure. For detailed instructions, see WeCom API authorization.

  2. If your organization has already bound a WeCom micro-app, you can select the checkbox to enable WeCom channel approval and then create an approval template.

  3. After creating the template, you can test its content. Select a recipient and click Send Test.

    image

  4. Click Confirm to complete the channel configuration.

Lark channel approval

After an organization administrator enables the approval flow and selects the Lark channel, you can initiate permission requests in Quick BI that are sent to Lark for approval.

  1. If your organization has not yet bound a Lark micro-app or authorized Lark API access, go to the configuration page to complete these steps as shown in the figure. For detailed instructions, see Lark API authorization.

  2. If your organization has already bound a Lark micro-app, you can select the checkbox to enable Lark channel approval and then create an approval template.

  3. After creating the template, you can test its content. Select a recipient and click Send Test.

    image

  4. Click Confirm to complete the channel configuration.