User Roles

Reporting provides the following user profiles:

• System Administrator: Users handling the tenants of a multi-tenant (cloud-deployed) system. They have the same access rights to the Admin tab that Administrators do, but typically don't interact with assets (reports, views, and data sources) in any way. They can only interact with these assets the way Viewers do, and they do not have access to e.g. the Data tab. They are in charge of creating and managing tenants in a Reporting instance. When initializing your Reporting instance, the System Administrator is the first user to be created, and whose role is to set up the rest of the system (tenants and administrators).

Note System Administrators are special and unique users created and configured on system initialization. They cannot be added, modified or deleted by Administrators, which manage all other users in a Reporting instance.

• Administrator: The role with the highest level of access in a tenant. Administrators can perform all actions in charge of general Reporting configuration, user and group management. The Administrator-level user can also view all the reports, views, and data models. They can manipulate ownership and subscriptions of these assets. However, Administrators cannot edit any content, such as reports or data models. Otherwise, Administrators can use and interact with assets in the same way a Viewer can.
• Data Designer: User role in charge of creating, modifying and sharing data sources needed for the creation of reports. Data Designers have full data access and distribute limited data access to Designer-level users, through data model design. In the context of system-wide access to data and users, this role has a lower access level than Administrators, but higher than Designers and Viewers.
• Designer: Designers are in charge of creating, modifying and publishing reports. The data available for components is limited by the data models that are shared with a Designer. This role has a lower access level than Administrators and Data Designers, but higher than Viewers.
• Power Viewer: Power Viewers can work with existing reports in order to create new views. However, they cannot create their own components or edit existing ones, only use them as a basis for views. In order to be able to do so, both the original component and its data source must be shared with the Power Viewer. Compared to a Designer, a Power Viewer has fewer options available to them even when they have all the permissions needed for asset editing. Other than that, they have the same access level and can use and interact with reports same as a Viewer can.
• Viewer: Users with this role can access shared reports, report views, modify the way data is displayed in them by using filters and settings (depending on the design of the asset), view, print and export reports, views . This is the lowest access level.