Permission Export Plugin-FineReport Help Document

Last update：June 17, 2024

Overview

Version

Report Server Version	Permission Export Plugin
11.0	V3.1.3

Application Scenario

Many enterprises value permissions and require regular permission audits to check whether assigned permissions comply with regulations.

Unfamiliarity with the previous permission assignment after personnel and administrator changes causes tough organization and management.

Function Description

By installing the Permission Export plugin, you can quickly audit permissions.

The Permission Export plugin automatically organizes user information and permission details. You can export Excel files with one click.

The Permission Export plugin automatically generates permission-related server datasets and supports parameter setting. You can directly call a dataset for the permission preview or task schedule.

Note:

When URLs are integrated into a permission management page, there is no export permission.

Plugin Introduction

Plugin Installation

You can obtain the plugin at https://community.finereport.com/plugin/?id=111.

For details about how to install the plugin in the designer, see Designer Plugin Management.

For details about how to install the plugin on the server, see Server Plugin Management.

Permission Export

1. Log in to the decision-making platform as a super admin and choose System Management > Permission Management > Permission Export.

For details about supported permission tables and table fields, see section "Permission Export Table."

Note:

Only the super admin can view the Permission Export tab.

2. Click the export button right to the related permission. A message will be pushed on the platform whether the export is successful or not. After the successful export, you can download the file by clicking the download button. /

Note:

1. If the export fails, a prompt message "Permission export failed. Try again." will be displayed.

2. For the table structure of the exported .zip file, see section "Permission Export Table."

Permission Dataset

After you install the Permission Export plugin, server datasets related to permissions are generated automatically, as shown in the following figure.

In the designer, you can choose Server > Server Dataset to perform the permission preview or task schedule operations by calling related datasets.

Some datasets can be parameterized. For details about the table structure and field definition, see section "Permission Export Table."

Permission Export Table

The tables supporting the permission export and permission audit are as follows.

Permission Table	Table Definition	Permission Export	Permission Dataset	Parameter in Permission Dataset
user_info	User information	Support	Support	Not support parameters. Use full data.
user_module	Users' permission to the platform management module	Support	Support	Not support parameters. Use full data.
user_entry	Users' permission to platform directory	Support	Support	Supports parameters. Username can be passed.
user_template	Users' permission to a single template	Support	Support	Supports parameters. Username can be passed.
user_connection	Users' permission to Data Connection	Support	Support	Not support parameters. Use full data.
role_entry	Roles' permission to the platform directory	Not support	Support	Supports parameters. Roles can be passed.
role_template	Roles' permission to a single template	Not support	Support	Supports parameters. Roles can be passed.
dep_role_entry	Departments' permission to the platform directory	Not support	Support	Supports parameters. Department paths can be passed.
dep_role_template	Departments' permission to a single template	Not support	Support	Supports parameters. Department paths can be passed.

Note:

The parameter values can be set to null, single, or multiple values. For example:

Parameter as null value: Fill in no data. Query full data.

Parameter as a single value: Fill in technical support. The queried parameter value is the technical support's permission.

Parameter as multiple values: Fill in technical support|sales department. (The string | is needed.) The queried parameter value is the permission of the technical support or sales department.

user_info

Note:

user_info does not contain the super admin's information.

Field	Definition	Notes
USERID	User ID	/
USERNAME	Username	/
REALNAME	Name	/
CREATIONTYPE	Creation type: 1. Manual creation 2. Synchronous creation	/
LASTOPERATIONTYPE	Last operation type: 1. Manual operation 2. Synchronous operation	/
DEPT_POST	Department and position Technical support-Director Department/Sub-department-Position: Technical support/Central region -Group member	If a user has multiple departments and positions, they will be concatenated, separated by \|, for example, Development-Maintenance engineer\|Technical support-Chief dispatcher.
ROLE	Role Example: Common role	If a user has multiple roles, they are displayed together, separated by \|, for example, Common role 1\|Management team.
MOBILE	Telephone number	/
EMAIL	Mailbox	/
ENABLE	Users' status: Enable Disable	/

user_entry

Users' viewing, editing, and authorizing permissions to the platform directory

Note:

1. Permissions of the homepage cannot be exported.

2. If a user has no viewing, editing, or authorizing permissions to a certain directory, no authorization record of the directory will be generated for the user.

Field	Definition
USERID	User ID
USERNAME	Username
REALNAME	Name
ENTRY	The location of directories under Directory Management > Directory List in the platform management system. Example: Profit Center/Project Command Room/Bank Dashboard
TEMPLATE_URL	Template storing path in the report project Example: demo/Dashboard/CEO Dashboard.frm Link: https://www.google.com/ Report tag: My Report Task
VIEWABLE	User's viewing permission to the directory yes: with viewing permission no: without viewing permission
EXPORTABLE	User's exporting permission to the directory FineReport project has no export permission, so the value of the EXPORTABLE field is no by default.
EDITABLE	User's editing permission to the directory yes: with editing permission no: without editing permission
AURHORABLE	User's authorizing permission to the directory yes: with authorizing permission no: without authorizing permission

user_template

Users' viewing and exporting permissions to the template in the report project after Authenticate Role Permission is enabled.

Note:

1. If Authenticate Role Permission is disabled, the exported content of user_template will be empty.

2. If a user has no viewing and editing permissions to a certain template, no authorization record of the template will be generated for the user.

Field	Definition
USERID	User ID
USERNAME	Username
REALNAME	Name
TEMPLATE_URL	Template storing path in the report project Example: demo/Dashboard/CEO Dashboard.frm
VIEWABLE	User's viewing permission to the template yes: with viewing permission no: without viewing permission
WRITABLE	User's reporting permission to the template yes: with editing permission no: without editing permission
EXPORTABLE	User's exporting permission to the template FineReport project has no export permission, so the value of the EXPORTABLE field is no by default.

user_connection

Users' using, managing, and authorizing permissions to the data connection after Data Connection Control is enabled.

Note:

1. If the admin does not enable Data Connection Ccontrol, the exported content of user_connection will be empty.

2. If a user has no using, managing, or authorizing permissions to the data connection, no permission record of the data connection will be generated for the user.

Field	Definition
USERID	User ID
USERNAME	Username
REALNAME	Name
CONNECTION	Data connection name in the report project.
USABLE	Users' using permission to the data connection yes: with using permission no: without using permission
EDITABLE	Users' managing permission to the data connection yes: with managing permission no: without managing permission
AURHORABLE	Users' authorizing permission to the data connection yes: with authorizing permission no: without authorizing permission

user_module

Uses' viewing and authorizing permission to the platform management module after Hierarchical Permission Management is enabled

Note:

1. If the admin does not enable Data Connection Control, the exported content of user_module will be empty.

2. If a user has no using and authorizing permissions to a certain platform management module, no permission record of the platform management module will be generated for the user.

Field	Definition
USERID	User ID
USERNAME	Username
REALNAME	Name
MODULE	Management module in data decision-making platform Example: User Management
USABLE	User's using permission to the platform management module yes: with using permission no: without using permission
AURHORABLE	User's authorizing permission to the platform management module yes: with authorizing permission no: without authorizing permission

role_entry

Users' viewing, editing, and authorizing permissions to the platform directory

Note:

1. Permissions of the homepage cannot be exported.

2. If a role has no viewing, editing, exporting, or authorizing permissions to a certain directory, no permission record of the directory will be generated for the role.

Field	Definition
ROLEID	Role ID
ROLE	Role
ENTRY	The location of directories under Directory Management > Directory List in the platform management system. Example: Profit Center/Project Command Room/Bank Dashboard
TEMPLATE_URL	Template storing path in the report project Example: demo/Dashboard/CEO Dashboard.frm Link: https://www.google.com/ Report tag: My Report Task
VIEWABLE	Roles' viewing permission to the directory yes: with viewing permission no: without viewing permission
EXPORTABLE	Roles' exporting permission to the directory FineReport project has no export permission, so the value of the EXPORTABLE field is no by default.
EDITABLE	Roles' editing permission to the directory yes: with editing permission no: without editing permission
AURHORABLE	Roles' authorizing permission to the directory yes: with authorizing permission no: without authorizing permission

role_template

Users' viewing, reporting, and exporting permissions to templates in the report project after Authenticate Role Permission is enabled.

Note:

1. If Template Authentication is disabled, the exported content of role_template will be empty.

2. If a role has no viewing, reporting, or exporting permissions to a certain template, no permission record of the template will be generated for the role.

Field	Definition
ROLEID	Role ID
ROLE	Role
TEMPLATE_URL	Template storing path in the report project Example: demo/Dashboard/CEO Dashboard.frm
VIEWABLE	Roles' viewing permission to the template yes: with viewing permission no: without viewing permission
WRITABLE	Users' reporting permission to the template yes: with editing permission no: without editing permission
EXPORTABLE	Roles' exporting permission to the template FineReport project has no export permission, so the value of the EXPORTABLE field is no by default.

dep_role_entry

Departments' viewing, editing, and authorizing permissions to the platform directory

Note:

1. Permissions of the homepage cannot be exported.

2. If a department has no viewing, editing, or authorizing permissions to a certain directory, no permission record of the directory will be generated for the department.

Field	Definition
DEP	Department and position Department: technical support Technical support-Director Department/Sub-department-Position: Technical support/Central region-Group member
ENTRY	The location of directories under Directory Management > Directory List in the platform management system. Example: Profit Center/Project Command Room/Bank Dashboard
TEMPLATE_URL	Template storing path in the report project Example: demo/Dashboard/CEO Dashboard.frm Link: https://www.google.com/ Report tag: My Report Task
VIEWABLE	Departments' viewing permission to the directory yes: with viewing permission no: without viewing permission
EXPORTABLE	Departments' exporting permission to the directory FineReport project has no export permission, so the value of the EXPORTABLE field is no by default.
EDITABLE	Departments' editing permission to the directory yes: with editing permission no: without editing permission
AURHORABLE	Departments' authorizing permission to the directory yes: with authorizing permission no: without authorizing permission

dep_role_template

Departments' viewing, reporting, and exporting permissions to templates in the report project after Authenticate Role Permission is enabled.

Note:

1. If Authenticate Role Permission is disabled in Template Authentication, the exported content of dep_role_template will be empty.

2. If Authenticate Role Permission is disabled in Template Authentication, the exported content of dep_role_template will be empty.

Field	Definition
DEP	Department and position Department: technical support Technical support-Director Department/Sub-department-Position: Technical support/Central region -Group member
TEMPLATE_URL	Template storing path in the report project Example: demo/Dashboard/CEO Dashboard.frm
VIEWABLE	Departments' viewing permission to the template yes: with viewing permission no: without viewing permission
WRITABLE	Departments' reporting permission to the template yes: with editing permission no: without editing permission
EXPORTABLE	Departments' exporting permission to the template FineReport project has no export permission, so the value of the EXPORTABLE field is no by default.

Previous：Permission Reuse

Next：Batch Role Authorization Plugin

Helpful
Not helpful
Only read

中文（简体）中文（繁體）日本語

English

Permission Export Plugin

Overview

Version

Application Scenario

Function Description

Plugin Introduction

Plugin Installation

Permission Export

Permission Dataset

Permission Export Table

user_info

user_entry

user_template

user_connection

user_module

role_entry

role_template

dep_role_entry

dep_role_template

Attachment List