Share dashboards with public links

1.1 Version

1.2 Application scenarios

After the user completes the dashboard, they often need to share it with others for viewing. If you don't have a platform account, how can you share it to make them visible?

1.3 Function introduction

After sharing the public link of the dashboard, anyone does not need to log in or have any data permissions. Click the shared link to view the dashboard. The public link also supports password access, avoiding the problem of data leakage, ensuring the convenience of the public link and also providing data security.

2.1 The administrator configures public link permissions

The public link function allows all users to make the dashboards they create public. This behavior may lead to internal data leakage. Therefore, only after the administrator opens the sharing permission of public links to ordinary users, can ordinary users share dashboards through public links.

For details on how the administrator configures permissions, please refer to: Public link permissions. 

Note: When sharing dashboards, you can also set "password protection" to further improve data security.

2.2 Create a public link

1）Click to view public link

Click "Dashboard", hover the mouse on the dashboard that needs to be shared, and click to open the "Create Public Link" button, as shown in the figure below:

2）Turn on the Share Link function. By default, the "Share Link" button is turned off, click to open "Share Link" to automatically generate a link, as shown in the following figure:

2.2.1 No password protection is set

Note: If you don't need to worry about data leakage, you can directly click "copy Link" to share the dashboard.

2.2.2 Set password protection

1）Check "Password Protection" to automatically generate a 4-digit password, click "Reset" to reset the password, and the password will take effect immediately after resetting, click "Copy Link and Password" to share the dashboard public link and password with other personnel. As shown below:

2）After clicking the Copy Link and Password, the copy content is as follows:

http://localhost:37799/webroot/decision/link/UPL1

Password: 80d9

3）Remove the password part, and then copy the link to the URL address bar of the browser to go to the dashboard password input interface.

2.3 Effect view

• No password protection

Password protection is not set, just paste and share the copied link, and other users can directly click the link to view the dashboard.

• Set password protection

If setting the password protection, after sharing the public link and password of the dashboard, click the public link and enter the password to view the dashboard. As shown below:

Note: Use the public link to share the dashboard with users. After the dashboard is modified, there is no need to send the sharing link again.

Note: After entering the wrong password 5 times (not including blank input), you will not be able to log in to the interface. You can re-enter the password after 1 minute to log in to the dashboard display interface. If you do not operate the dashboard for 10 minutes, you need to re-enter the password to log in.

If the previously created public link does not want other people to visit it again, you can also go to the place where the public link was created and click to close this public link button. As shown below:

Note: There is no time limit for the created public link, and it can take effect until the link is closed.

3.1 PC side

After the button is closed, the public link created before becomes invalid, as shown in the following figure:

3.2 Mobile

Turn off the Share Link button. After the public link on the mobile terminal becomes invalid, the link can no longer open the dashboard when the page is refreshed.

You can view the dashboards with public link enabled in a unified manner. Open "Dashboard" and select "BI-Dashboards_Public_Link_Dashboards", as shown in the figure below:

5.1 Local Area Network

Open the shared public connection. When the dashboard has a linkage effect, it will appear in the upper right corner. Click the floating button to reset the dashboard and clear all linkages. As shown below:

5.6 Templates accessed by public links, need to log in after jumping

Problem phenomenon: The server reports an error: Problem phenomenon: The public link jumps to the sub-template, and the sub-template needs to log in.

Reason: In order to prevent data leakage, the viewing authority and data authority of the sub-template after the public link jumps are based on the authority of the login person.

Solution: When the dashboard settings jump to other dashboards, choose to add the public link URL of the target dashboard to visit. This setting can avoid the need to log in when a dashboard opened using a public link jumps to another dashboard. Reference document: Jump

5.7 Replace IP

If the user installs the bi project locally, it is not deployed on a server that can be accessed from the external network. For example, the access address is: http://localhost:37799/webroot/decision.The generated public link of the dashboard is also a link starting with localhost, as shown in the following figure:

This link is directly copied and shared to users who are not on this machine. It is impossible to access it. You need to change the localhost to the IP of the current server.

5.7.1 View IP

• The IP of the Windows server can be obtained by referring  to how to check your own IP in Windows;

• The IP of the Linux server can be obtained by referring  to how to check your own IP in Linux.

5.7.2 Modify localhost to IP 

For example: The IP of the machine installed by FineBI is 120.20.29.224 

• The public link originally obtained is:

http://localhost:37799/webroot/decision/link/brQ7

• After replacing the IP, the link is:

http://120.20.29.224:37799/webroot/decision/link/brQ7

5.8 Create firewall port inbound rules

If the FineBI port used by the user is not 37799, you need to change the special local port to the user's own port number in the firewall inbound rules. 

To create firewall port inbound rules under Windows, please refer to firewall inbound  rules.