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.
See the Considerations section below for important considerations regarding the Permissions Enablement Tool.
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.
Click here to download the Reporting 2.0 Starter Guide.
Permissions
For more 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 which permissions users need to have to create and view reports.
Considerations
- When Reporting 2.0 permissions are added to a security role through the Permissions Enablement 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).
- The Permissions Enablement Tool does not support system-defined security roles, only organization-defined security roles. If you need to migrate Custom Report permissions from any system-defined roles (both standard and dynamic), this must be done manually.
- User-level constraints are not supported by the Permissions Enablement Tool. If you have defined any constraints on the user level that need to be retained, this must be done manually. See View Permissions - User Record.
Enable Permissions
The Reporting 2.0 Permissions Enablement page displays a list of all organization-defined security roles in the portal that have at least one Custom Report permission included. System-defined security roles are not supported by this tool. 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
What happens to permission constraints that were assigned to the Custom Reports permissions?
All permission constraints that were included in the Custom Reports permissions are also migrated to the Reporting 2.0 permissions.
What happens if an equivalent Reporting 2.0 permission is already included in a security role?
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.
Will the permissions enablement tool disable any of the custom report permissions I have set up in my portal?
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: