The Reporting 2.0 Permissions Enablement page allows administrators to enable the equivalent Reporting 2.0 permissions to be added automatically to applicable security roles when a report is migrated from Custom Reports to Reporting 2.0. This instantly gives users the permissions they need to create and view migrated custom reports, without administrators having to assign the permissions manually once a custom report is migrated.
Note: When Reporting 2.0 permissions are added to a security role through the permissions migration tool, the Custom Reports permissions are not removed. The Custom Reports permissions remain assigned to the security role and will continue to be available until the Custom Reports functionality is deprecated in 2022 (the exact date will be announced closer to the deprecation).
To access the Reporting 2.0 Permissions Enablement page, go to. This page can only be accessed by the top-level system administrator in the portal.
For information about Reporting 2.0 permissions, see the following:
The Reporting 2.0 Permissions Enablement page displays a list of all security roles in the portal that have at least one Custom Report permission included. To enable the equivalent Reporting 2.0 permissions to be added to security roles when a report is migrated from Custom Reports to Reporting 2.0, perform the following steps:
- Select one or more security roles from the list.
- Click . This executes the process of migrating the Reporting 2.0 permissions that are equivalent to the Custom Report permissions. The Reporting 2.0 permissions added to the security roles that are selected.
Once the migration is completed, the Status of the Last Import column updates to "Success," indicating that the Reporting 2.0 permissions have been added to the security roles that were selected.
The Last Imported column updates to the date on which the successful import occurred.
The permission migration process is permanent and cannot be reversed through the permission migration tool.
Frequently Asked Questions
All permission constraints that were included in the Custom Reports permissions are also migrated to the Reporting 2.0 permissions.
The Reporting 2.0 permissions that are already included in the security role will remain.
If a permission has constraints prior to being added to the security role, and the existing equivalent permission does not have constraints, the constraints will be added to the existing permission when the enablement process is complete.
No. No changes will be made to the custom report permissions that you have configured in your portal. Permissions are never removed in this process.
Custom Reports Permissions with No Equivalent Reporting 2.0 Permission
The following table shows the Custom Reports permissions that have no equivalent Reporting 2.0 permissions:
|Last Published: 9/10/2021||If you have feedback or suggestions for an Online Help article, please select this link.||© 2021, Cornerstone OnDemand|