Resource Handover

Applicable crowd: super administrator

Note: Sub-administrators cannot perform management operations related to resource handover under "Data Decision System > Management System".

1. Version 

2. Application scenarios

When a user in the enterprise leaves or transfers jobs, the dashboards and data sets created by the user need to be handed over to other users for continued use and editing.

3. Function introduction

The administrator can transfer all or part of the data sets and dashboards created by one user to another user in batches, and allow the other user to freely use, edit and reference these analyses just like the original user.

1. User Type

The two user types are recommended to be consistent when handing over resources , such as handover between data processing users and data analysis users. Different user types do not affect the table that will be handed over successfully, but may affect subsequent analysis. For details of user types, see: BI Design User , BI View User

2. Data permissions

data connection permissions will be inconsistent due to different department roles , and the data may not be available after the handover. HYPERLINK "https://help.finebi.com/doc-view-488.html" \t "_blank"

Common user resource handover means that when the user is not deleted from user management, the administrator transfers some or all of the dashboards and data sets created by the user to other users for use.

In this example, the user Anna needs to hand over all the dashboards and data sets made by the user to eoco because of the transfer.

1. Concept Description

1) Data set handover storage location

2) Dashboard storage location

The position after handover is placed according to the original relative path before handover.

2. Selecting the surrendering party

administrator logs in to the data decision-making system, selects Manage > Resource Handover , selects the common user , and selects the handover party as the eoco user, as shown in the following figure:

Scope of optional users for the surrendering party: all users (including super administrators)

3. Selecting handover resources

1) Handover Dashboard

After selecting a user, all dashboards created by the user will be displayed. Select the dashboard to be transferred, as shown in the following figure:

Note: Dashboards after handover to the recipient will be stored in the newly created folder each time, not in the folder already created by the previous handover.

2) Handover dataset

Click the "Spider" tab and select the extracted data set to be transferred, as shown in the following figure:

Note: The real-time data here and the corresponding data type under the corresponding data extraction are prepared. It is determined by the BI project purchased by the user. For details, see: Introduction to Real-time Data & Extracted Data . The example gives the extraction data set handover, and the real-time data handover operation is the same.

4. Select recipient

Receiver optional user range: BI design users (excluding super administrators)

1) Select the receiver as Tom, as shown below:

2) Click OK , and a dialog box will pop up Sure to handover resource of "eoco(eoco)" to "Tom(Tom)"? , click OK , as shown in the following figure:

3) If the user types or user department roles are inconsistent, a prompt will pop up, click OK , as shown in the following figure:

Note 1: If the handover fails, it will prompt: The system is abnormal, the handover fails, and the specific exception information has been written into the system log.

Note 2: If there are resources that cannot be handed over due to exceptions, the system will automatically skip the failed resources and continue to hand over the remaining resources.

5. Effect View

1) Dashboard for Handover

1) Log in with the Tom user account, and you can see that the dashboard handed over by eoco appears in the dashboard. The folder is the dashboard handed over to the Tom user this time, as shown in the following figure:

2) If Tom has the corresponding permissions, you can edit and share the dashboard, as shown in the following figure:

2) Handed over datasets

Log in with the Tom user account, and under Data Preparation > Extract Data Tab, you can see that the data set handed over by eoco appears in my self-service dataset. The business package is the data set handed over to the eoco user this time, as shown in the following figure:

Under the Retail, you can view the datasets handed over under the common business package, as shown in the following figure:

A deleted user means that the user is deleted from the user management, and the administrator transfers some or all of the dashboards and data sets made by the user to other users for use.

Note: If the handover is not performed, when other users edit the dataset, the prompt: save failed, user unknown, key: unknown user, cause: get null user object

This example creates a dashboard for eoco user handover to Anna user.

1. Operation steps

1) The administrator logs in to the data decision-making system, selects Manage > Resource Handover , selects the deleted user , selects the handover party, selects the dashboard to be transferred out, and selects the recipient as the Anna user, as shown in the following figure:

2) Click OK , and a dialog box will pop up Sure to handover resource of "Unknown User 1" to "Anna(Anna)"? , click OK , as shown in the following figure:

2. Effect View

1) Log in with the Anna user account, and you can see that the dashboard handed over by Alice appears in the dashboard. The folder is the dashboard handed over to the Anna user this time, as shown in the following figure:

2) If Anna has the corresponding permissions, she can edit and share the dashboard, as shown in the following figure:

The method of handing over live datasets and extracting datasets is the same as the dashboard.

1. Data connection permissions

For extracting datasets, if the receiving resource user does not have the corresponding data connection permission , the receiving resource user cannot add SQL datasets and database tables from the data connection.

2. Dashboard Sharing

If both the receiving resource user and the submitting resource user have permission to share dashboards:

• If the shareable user permissions are the same, the receiving resource users can share as normal as before;

• The permissions of the users who can share are inconsistent, and the intersection of the user who has shared the resource and the user who can receive the resource can be shared;

If the user who receives the resource does not have the sharing permission, and the user who handed over the resource has the permission to share the dashboard, you need to enable the sharing permission of the dashboard for the user who accepts the resource after the handover .

3. Self-service dataset sharing

The self-service dataset sharing permission rules are the same as the dashboard sharing permissions in Section 4.2.

4. Hanging out the dashboard

For the dashboards that have been hung out or are applying to be hung out, the original state is still maintained after the handover, but the relevant information is changed to receive the information of the dashboard user.

5. Public Links

If the receiving resource user does not have permission to open public links before handover, you need to enable public link permissions for them , otherwise the public links on the dashboard will be displayed as closed.