By default, configuring permissions on a dataset determines the permissions for reports and views based on that dataset. However, in some cases you may want to allow users to view aggregated or filtered data in a report or view, without providing access to the underlying dataset. You can configure additional permissions on a specific report or view to grant access to groups who do not have access to the dataset.

The Report and View Permissions page allows you to explicitly set the permissions required to view an individual Report or View.

  • In a study, select (Admin) > Manage Views.
  • The Access column shows links for the type of security applied to each view:
    • public: visible to anyone with read access to the folder.
    • private: visible to the creator only
    • custom: permissions have been configured per group/user
  • Click the link for the view of interest:

The Report and View Permissions page looks like the following screenshot. There are three options for configuring report and view permissions:

  • Default : this dynamic view will be readable only by users who have permission to the source datasets
  • Custom : set permissions per group/user. Use check boxes to grant access.
  • Private : this view is only visible to you
  • Select desired permissions.
  • Click Save.

In the lists of site and project groups, an enabled group indicates that the group already has Read access to the dataset (and to this report) through the project permissions. If a group is disabled, the group does not have Read access to the dataset and cannot be granted access through this view.

Related Topics


Was this content helpful?

Log in or register an account to provide feedback

expand all collapse all