Overview
Version
FineDataLink Version | Functional Change |
---|---|
4.1 | Added the Data Development User configuration in User Management. This setting, in conjunction with the registered license, controlled the number of FineDataLink users. |
Function Description
FineDataLink has a predefined set of users, with configured details such as basic information, departments, positions, roles, and platform access settings.
Log in to the FineDataLink as the admin and choose System Management > User Management. You can go to four tab pages: All Users, Department, Role, and Platform User, as shown in the following figure.
User Adding
You can add users using the following three methods.
Method | Description | Help Document |
---|---|---|
Manually adding users | You need to manually enter a user's information, department, and role. You can edit, disable, and delete users. | |
Importing users | You can import a user's information, department, and role from a server dataset. You can edit, disable, and delete users. | |
Synchronizing users | You can synchronize a user's information, department, and role from a server dataset. A system can only synchronize data from one dataset at a time. You cannot edit users when User Editability is disabled. You can disable the synchronized users, but you cannot delete them. |

Department
The Department tab page is used for company department management, including the management of departments, positions, and personnel.

Department Management
Adding a Department
In Department List, select a manually added department, click the icon in the upper right corner, enter the department name, select the superior department from the drop-down list of Superior Department, and click OK to add a sub-department, as shown in the following figure.

The Superior Department dropdown excludes departments generated through user synchronization.
Adjusting the Department Hierarchy
You can modify the superior department and the hierarchical structure of manually added departments.
For example, you can reassign Audit Team, a sub-department of Finance Group 1, to Finance Group 2 as its sub-department.
Hover the cursor over Audit Team, click the icon, adjust the superior department by selecting Finance Group 2 from the drop-down list of Superior Department, and click OK, as shown in the following figure.
Audit Team then becomes a sub-department of Finance Group 2. The positions and users in Audit Team are also moved accordingly.
Renaming a Department
Hover the cursor over a department, click the icon, rename the department, and click OK.
Changes in department names do not affect the configured permission.
Deleting a Department
Hover the cursor over a department, click the icon, and click OK. The department and its sub-departments will be removed from Department List.
Positions in a deleted department still exist in the position list of the system, and the admin can assign these positions to other departments.
Users in a deleted department still exist in the user list. However, the deleted department will be removed from Dept.-Posit.
Editing Department Users
You (the admin) can assign specific users to each department that is not synchronized from server datasets.
Select a department other than All Departments and click Edit User in the upper right corner. The personnel management dialog box will pop up, as shown in the following figure.
You (the admin) can add or delete users in a department. You can select or deselect all users with one click, as shown in the following figure.
You can click users in Unselected User to move them to Selected User.
Similarly, you can click users in Selected User to move them to Unselected User.

After selecting a department, you can view the users belonging to the department in User List.

Position Management
Adding a Position
Select a department and click the icon in the upper right corner of Position List. In the pop-up Edit Position window, you can add, delete, or modify positions for the department, as shown in the following figure.
The checkboxes represent the positions generated through user import, which you can select to assign to the department. The positions generated through user synchronization cannot be selected.
You can quickly find the required position generated through user import using the search box. If a position is not found after searching, you can click the
icon to add it.
Deleting a Position
Hover the cursor over a position, click the icon, and click OK. The position will be removed from Position List in the corresponding department.
Deleted positions still exist in the position list of the system, and the admin can assign these positions to other departments.
For example, the Finance Team Leader position exists in both Finance Group 1 and Finance Group 2. If you (the admin) delete the Finance Team Leader position from Finance Group 2, it will not affect the same position in Finance Group 1.
Editing Position Users
You (the admin) can assign specific users to each position.
Select a position under a department and click Edit User in the upper right corner. The personnel management dialog box will pop up, as shown in the following figure.
You (the admin) can add or delete users in a position. You can select or deselect all users with one click, as shown in the following figure.
You can click users in Unselected User to move them to Selected User.
Similarly, you can click users in Selected User to move them to Unselected User.

Role
The Role tab page is used for role management and personnel management.

Role Management
On the Role tab page, click the icon in the upper right corner of Role List to add a role to the system, as shown in the following figure.
You (the admin) can assign specific users to each role.
Select a role and click Edit User in the upper right corner of User List. The personnel management dialog box will pop up, as shown in the following figure.
You (the admin) can add or delete users in a role. You can select or deselect all users with one click, as shown in the following figure.
You can click users in Unselected User to move them to Selected User.
Similarly, you can click users in Selected User to move them to Unselected User.
You can add users to built-in roles (roles not added through user synchronization) in batches.
Click Batch Add, enter the usernames in the pop-up box, separate each username with a comma (,), and click OK, as shown in the following figure.
1. All users are added successfully.
If all users are added successfully, the prompt "N user(s) added successfully" will be displayed, as shown in the following figure.

Users with duplicate usernames are regarded·as the·same user·and deduplicated after successfully added.
Users who have already been assigned to the role will still be counted if they are added again in a batch-adding process.
Users successfully added to the role will be automatically moved from Unselected User to Selected User, as shown in the following figure.
2. Some users failed to be added.
If the following situations exist, the users may fail to be added.
Usernames that do not exist on the platform cannot be added. Sub-admins cannot add users who are not within their management scope.
If spaces exist before or after the "," separator, the system will automatically remove them before matching the username. If a username starts or ends with spaces, the username matching will fail, and the user cannot be added.
If the FineDB database type is Db2, MySQL, or SQL Server, and the username has a trailing space, the username can still be successfully matched and added as a user.
If a username contains a comma (,), the comma will be treated as a separator, splitting one user into two users. If these two users do not exist on the platform, they will fail to be added.
If some users fail to be added, the prompt "N user(s) added successfully, N user(s) added failed" will be displayed. You can click Details to view the users who failed to be added, as shown in the following figure.

1. Users with duplicate usernames are regarded as the same user. Users are deduplicated when added successfully or fail to be added.
2. Users who have already been assigned to the role will still be counted if they are added again in a batch-adding process.
Users successfully added to the role will be automatically moved from Unselected User to Selected User, as shown in the following figure.
Platform User
User Type | Description |
---|---|
PC User | The default classification for all users on the platform When User Restriction is enabled, only the selected users can log in to the platform, and all other users are prevented from logging in. 1. By default, PC users are not restricted, meaning that all users are PC users and can log in to the platform. 2. User Restriction is enabled by default only when the registered license has a limit on the user quantity of the decision-making platform. |
FDL Users | A subgroup of PC User, based on the product used When FineDataLink and FineBI are deployed in an integrated manner, PC User includes BI User and FDL User. |
Data Development User | A subgroup of FDL User When User Restriction is enabled, only data development users can use functions such as Data Pipeline, Data Development, Data Service, and Task O&M. Other PC users cannot use these functions. ![]() |
PC User
User Adding
On the corresponding platform, you can edit which users are allowed to access the platform.
Click Edit User in the upper right corner, as shown in the following figure.
Enable User Restriction and select the required users, as shown in the following figure.
Effect Display
Users not in the corresponding list cannot log in to the platform.
For example, if the user Alice is enabled but not included in PC User, she cannot log in to the platform, as shown in the following figure.
User Restriction Disabling
After disabling User Restriction for PC User, no restrictions exist on platform users.
After you re-enable User Restriction, the previous user restriction configuration takes effect.
PC User Limit
If the system is registered, the registration file will restrict the number of PC users. The maximum number of PC users limited by the registration file and the number of PC users currently added will be displayed, as shown in the following figure.

1. If the system is not registered, no limit applies to the number of platform users.
2. If the number of added users exceeds the limit, the remaining unselected users will be grayed out.
3. During user editing, if the user limit is reached due to actions by other admins, you cannot continue adding users, and a prompt will appear, indicating that the number of users of this type has reached the limit and cannot be added further due to actions by other admins.
Data Development User
Adding a User
On the corresponding platform, you can edit which users are allowed to access the platform.
Click Edit User in the upper right corner, as shown in the following figure.
Enable User Restriction and select the required users, as shown in the following figure.

If the user Lisa is enabled but not listed under Data Development User, even if she is assigned permissions such as Use Permission on Data Platform and Management Permission on Scheduled Task, she still cannot use Data Pipeline, Data Development, Data Service, and Task O&M after logging in.
Disabling User Restriction
After User Restriction for Data Development User is disabled, the user restriction will be lifted.
Registration Status and Control Logic Description
Status | Control Logic |
---|---|
Not registered/Registration failed | By default, User Restriction is disabled, meaning that all PC users can use Data Pipeline, Data Development, Data Service, and Task O&M. You can manually enable User Restriction. After enabling it, you can configure PC users as data development users, with unlimited user quantity. |
Successful registration | If Data Development User in the license is set to Unlimited, the control logic is the same as when the system is not registered. If Data Development User in the license is not Unlimited: 1. User Restriction is enabled by default and cannot be manually disabled. 2. The maximum number of data development users is determined by the license, and the super admin is treated as a data development user by default. |
Registration expired | The previous configurations and control effects will be kept. |