Distribute reports to provide business information to other users.

Report access control

You can control who sees reports by applying a security state. You can make reports that are:
  • Globally visible to all users
  • Visible only to you if you are the report creator.
  • Visible to one or more specific roles
  • Visible to one or more specific users or groups

Sharing by user, group, or role, is the primary method of sharing reports. You can use access control lists (ACLs) to control access to the underlying table or database view data. Users are able to view reports when the user does not have access rights to a data record in a data source or source table of a report. However, they are not able to see that record in a list view or in a drill-down view. Database-view-list reports require the reporting user to satisfy ACLs on the target data to view records in the list. Users without sufficient permissions see filtered list reports.

Note: ACLs for a table do not propagate to database views based on that table. Database views require separate ACLs.

Reports that present aggregate data, such as pie or bar reports, do not require the user to satisfy target table ACLs to view the report. ACLs are required to view the list of records when you select a portion of a report visualization. When you have access to a report but not to some of its records, you do not see those records in a drill-down list or in a list view of the data in the report. However, they are included in visualizations of data.

If a user saves a global report as a group or personal report, the platform copies the report rather than changing its security state. Copying the report enables users who cannot create their own global reports to modify a global report, and then save a personal version of the report.

If a user opens a personal report and tries to save it as a group or global report, the security state is changed rather than copying the report.