Prior to this release the Reporting 2.0 Granular permission model was a complex model and sometimes confusing. It can be difficult to understand which permissions and constraints apply to which reports, and which need to be assigned to users to allow them to see the appropriate reports and data. For customers with less complex reporting needs, a simpler permission model is needed, one that will allow them to quickly grant access by report type, similar to what was available with Custom Reports.
With this release, a new Reporting 2.0 Report Level Permission Model is generally available to all customers, in addition to the already existing Reporting 2.0 Granular Permission Model. Customers can choose whether to keep the existing Reporting 2.0 granular permissions, or to start using the new, simpler, report level permissions.
Switching to the new model is optional, migration options and validation tools will be available to support customers with the initial setup.
Customers still using Custom Reports can migrate Custom Report permissions and constraints to the new Reporting 2.0 Report Level Permission Model or the Reporting 2.0 Granular Permission Model for the following reasons:
- Reporting 2.0 Granular Permission Model
- Provides customers a lot of flexibility
- Allows for complex permission configurations
- Hundreds of permissions
- Reporting 2.0 Report Level Permission Model
- Two permissions per report type: View and Manage
- Each Report type permission has its own set of constraints
- A user having permission for a report type can see any reports shared with them that match the report type
The table below lists the new permissions:
Customers choose to opt-in by using the Reporting 2.0 Permission Enablement tool to migrate to the new permission model. This tool is located in Core Preferences and guides customers through the process with clear documentation explaining how the permission migration takes place and which Custom or Granular Report permissions and constraints map to which Report type permissions.
When the August ’22 Release is deployed on August 5, four migration options will be available:
- Custom Report Permissions > Reporting 2.0 Report Level Permissions
- Custom Report Permissions > Reporting 2.0 Granular Permissions
- Reporting 2.0 Granular Permissions > Reporting 2.0 Report Level Permissions
- One Reporting 2.0 permission model can be active per portal: the traditional Reporting 2.0 Granular Permission Model or the simplified Reporting 2.0 Report Level Permission Model.
- Once a portal is shifted to the new Reporting 2.0 Report Level Permission Model, it cannot be reverted to the Reporting 2.0 Granular Permission Model.
- Permissions and constraints are not the same in the two models, therefore users may see different data after migration. It is advised to take note of the mapping used in the migration tool and evaluate the impact upon users. There may be instances where users see more or less data following migration.
- Constraints defined at the user level are not migrated. Constraints assigned to Custom Report and Reporting 2.0 granular permissions at the user level will need to be migrated manually by customers if they need to be maintained.
Permissions in Reporting 2.0 are different than the permissions for Custom Reports. Custom Reports had a "Manage" permission for creating and editing reports and a "View" permission for viewing reports. This is similar to Reporting 2.0 report level permissions if users opt in, but different from Reporting 2.0 granular permissions where users need to be given multiple permissions in order to create or view reports.
It is important to be aware of the differences between permissions in Reporting 2.0 and those in Custom Reports so that users have all necessary permissions to begin using Reporting 2.0.
For more information about Reporting 2.0 permissions, see the following: