Overview
Version
| Report Server Version |
|---|
11.0 |
Application Scenario
The decision-making platform allows you to set departments/roles/users, through which admins can restrict template access permissions.
For large systems with many users and a limited number of templates, permission configuration by roles can be used when template permission control is required.
Function Description
If a template permission is configured for users of certain roles, to view the template, the users must log in to the decision-making system first, and then the system will check whether the logged-in users have the permission to access the template according to their departments/roles/usernames.
| Example | Scenario | Step |
|---|---|---|
Example One | After enabling Template Permission, you (the super admin) can grant eoco the permission to view GettingStartedEN.cpt in the project. | 1. Enable Template Permission and select Authenticate Role Permission. 2. Assign the View permission on templates in Template Authentication. |
Example Two | After enabling Template Permission, you (the super admin) can grant eoco (the sub-admin) the permission to manage template authentication. eoco can assign the View permission on GettingStartedEN.cpt in the project to the Technical support department. | Log in to the decision-making system as the super admin: 1. Enable Template Permission, and select Authenticate Role Permission. 2. Assign the View permission on templates to the sub-admin in Template Authentication. 3. Enable Hierarchical Authorization. 4. Assign the Authorization permission to the sub-admin in Personnel Management. 5. Assign the Use permission to the sub-admin in System Management. Log in to the decision-making system as the sub-admin: 6. Assign the View permission on templates to users in Template Authentication. |
Example One
This section takes the following scenario as an example. After enabling Template Permission, you (the super admin) can grant eoco the permission to view GettingStartedEN.cpt in the project.
Selecting an Authentication Method
Log in to the decision-making platform as the super admin, choose System Management > Template Authentication, click the 
icon, enable Template Permission, select Authenticate Role Permission, and click Save, as shown in the following figure.
Click Select and configure authentication for templates as needed, as shown in the following figure.
By default, authentication is required for all templates. Switching the lock icon to the locked state indicates that authentication is not required for the selected template.
Note:
Assigning the View Permission in Template Authentication
Log in to the decision-making platform as the super admin, choose System Management > Template Authentication > Common Permission Configuration, and select the dept./role/user to be assigned the permission to.
In this example, select eoco and assign the View permission on GettingStartedEN.cpt to eoco, as shown in the following figure.
Note:
Effect Display
1. Enter http://localhost:8075/webroot/decision/view/report?viewlet=GettingStartedEN.cpt in a browser and log in using eoco's account, as shown in the following figure.
2. Enter http://localhost:8075/webroot/decision/view/report?viewlet=GettingStartedEN.cpt in a browser and log in using another account without the View permission on GettingStartedEN.cpt. In this case, the template cannot be accessed, as shown in the following figure.
Example Two
This section takes the following scenario as an example:
After enabling Template Permission, you (the super admin) can grant eoco (the sub-admin) the permission to manage template authentication.
eoco can assign the View permission on GettingStartedEN.cpt in the project to the Technical support department.
Selecting an Authentication Method
Log in to the decision-making platform as the super admin, choose System Management > Template Authentication, click the icon, enable Template Permission, select Authenticate Role Permission, and click Save, as shown in the following figure.
Click Select and configure authentication for templates as needed, as shown in the following figure.
By default, authentication is required for all templates. Switching the lock icon to the locked state indicates that authentication is not required for the selected template.
Note:
Do not create a top-level directory named reportlets in the WEB-INF/reportlets path of the project. Otherwise, the template tree cannot be loaded.
Assigning the Authorization Permission in Template Authentication
Log in to the decision-making platform as the super admin, choose System Management > Template Authentication > Authorization Configuration, and select the dept./role/user to be assigned permission to.
In this example, select eoco and assign the Authorization permission on GettingStartedEN.cpt to eoco, as shown in the following figure.
Note: The Authorization permission in Template Authentication determines which template permission can be assigned to users by the sub-admin during management.
Enabling Hierarchical Authorization
Log in to the decision-making platform as the super admin, choose System Management > Permission Management, click the icon, enable Hierarchical Authorization, and click Save, as shown in the following figure.
Note:
Assigning the Authorization Permission in Personnel Management
Log in to the decision-making platform as the super admin, choose System Management > Permission Management > Authorization Configuration, and select the dept./role/user to be assigned the permission to. Select eoco in this example.
Click the Personnel Management tab and assign the Authorization permission on Technical support to eoco, as shown in the following figure.
Assigning the Use Permission in System Management
Log in to the decision-making platform as the super admin, choose System Management > Permission Management > Common Permission Configuration, and select the dept./role/user to be assigned the permission to. Select eoco in this example.
Click the System Management tab and assign Use permission on Template Authentication, as shown in the following figure.
Assigning the View Permission in Template Authentication
Log in to the decision-making platform as the sub-admin eoco and choose System Management > Template Authentication > Common Permission Configuration.
The department and template available for permission assignment are Technical support and GettingStartedEN.cpt configured in the "Assigning the Authorization Permission in Personnel Management" section and the "Assigning the Authorization Permission in Template Authentication" section.
In this example, you (eoco) can assign the View permission on GettingStartedEN.cpt to the Technical support department, as shown in the following figure.
Effect Display
1. Enter http://localhost:8075/webroot/decision/view/report?viewlet=GettingStartedEN.cpt in a browser and log in using the account of Anna from the technical support department, as shown in the following figure.
2. Enter http://localhost:8075/webroot/decision/view/report?viewlet=GettingStartedEN.cpt in a browser and log in using another account without View permission on GettingStartedEN.cpt. In this case, the template cannot be accessed, as shown in the following figure.
Notes
When Template Permission is enabled:
1. Template authentication is not required when users view directory templates on the decision-making platform.
2. Template authentication is required when users view homepage templates on the decision-making platform.
If template A is mounted on the homepage, a user cannot view the template on the homepage without the permission on the template.
