Reporting 2.0 Permissions Enablement Page

This functionality is only available in Stage portals until the October '20 Release on 30 October 2020. This functionality is not currently available in Pilot or Production portals.

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.

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 with the February '21 release.

To access the Reporting 2.0 Permissions Enablement page, go to Admin > Tools > Core Functions. 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:

  • Permissions in Reporting 2.0 - This provides detailed information about Reporting 2.0 permissions.
  • Permissions List - This provides the list of permissions and their relationships so that you know the specific permissions users need to create and view reports.

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:

  1. Select one or more security roles from the list.
  2. Click Confirm. This executes the process of migrating the Reporting 2.0 permissions that are equivalent to the Custom Report permissions.
  3. Once the process is completed, a confirmation page opens. Click Confirm to confirm that you want the Reporting 2.0 permissions added to the security roles. This completes the migration process.

Once the migration is completed, the confirmation page lists all the security roles that were included in the migration. 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.

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:

Custom Reports Permission Reporting 2.0 Permission Conditions
Calculated Fields - Modify No equivalent permission  
Calculated Fields - View No equivalent permission  
Custom Multi-Module Report - Create No equivalent permission; will be handled by entities  
Custom Multi-Module Report: View No equivalent permission  
Report Delivery - Email (Note: This is a permission that cannot be constrained.) Reporting - Email Delivery  
Report Delivery - FTP Reporting - FTP Delivery  
Reports inside a folder - Share Reporting - Share  
N/A Reporting - View This permission will be enabled for all security roles that have a View permission from any Custom Report.
N/A Reporting - Manage This permission will be enabled for all security roles that have a Create permission from any Custom Report.
N/A Reporting - System Templates This permission will be enabled for all security roles that have a Reporting - View permission.
N/A Reporting - Download This permission will be enabled for all security roles that have a View permission from any Custom Report.