--- sourceDocument: Australia Platform Analytics sourceDocumentLink: https://www.servicenow.com/docs/r/australia/now-intelligence Release : - australia ft:locale : - en-US ft:publication_title : - Australia Platform Analytics ft:clusterId : - par bundleId : - par workflow : - Platform --- # Report permission issues # Report permission issues {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Report permission issues This guide explains common reasons why reports in ServiceNow may display less data than expected or no data at all, focusing on permission and sharing settings. It addresses issues related to report visibility, data restrictions caused by access controls, and changes introduced in the Australia release to enhance report security. Show full answer Show less ## Report Sharing and Visibility * By default, new reports are private and visible only to the creator or administrators. * Reports must be explicitly shared with users, groups, or roles to be accessible. * Unshared reports do not appear in users' report lists or selection options. * If a user sees a dashboard with a report but cannot access the report directly, a message indicates it is only visible to specific users or groups. * Report owners or administrators can share reports using the report's sharing icon to grant appropriate access. ## Data Display Differences in Reports * **List reports:** Users may see fewer rows due to read access control lists (ACLs) applied to each record; some rows may be removed based on security constraints. * **Graphical/non-list reports:** Data differences occur because of Before Query business rules on source tables that filter data based on user permissions, resulting in varying report results for different users. ## Changes in the Australia Release * All public Core UI reports are unpublished by default to improve security. * The system property `glide.report.publishedreports.enabled` is set to false for all Core UI reports. * Users with the `reportadmin` role can view and manage unpublished reports in the Reports Public \[sysreportpublic\] table. * Report admins can re-enable public access or share reports with logged-in users as needed. * To restrict reports to logged-in users only, set sharing to "Everyone" without publishing the report. There are several reasons why a report is showing less information than expected or possibly no data at all. These include insufficient permissions on the report and the report not being shared. ## Report not shared {#report-permission-issues__section_vth_lvn_1vb} A common reason that a report may not be viewable is that the report hasn't been shared with the users who are attempting to access it. By default, a newly created report won't be shared and therefore inaccessible to anyone except the report creator or users with the admin role. A report can be shared with an individual user, with one or more groups, or assigned to one or more roles. Unshared reports don't appear in lists of reports a user has access to or in other options in which a report might be opened or selected. When users are able to see a dashboard the report has been added to, but not the report itself, a message indicates that the "Report is visible only to a specific user or group". To correct this issue, the owner of the report (or an administrator) can share that report with the individuals who should have visibility and access to that report. You can share a report directly from the report's sharing icon. For more information, see [Share a Core UI report](https://www.servicenow.com/docs/dbGEOlwIH~2ssqzRKvI2mA "Control which users and groups can see a Core UI report."). ## List reports show fewer rows than expected {#report-permission-issues__section_hzw_ywn_1vb} Another common issue is that fewer rows appear in list reports than the viewer expects. For example, one user sees 100 rows in a list report, but another user, viewing that same report may see fewer rows or even no rows at all. When one or more rows have been removed from the report, a message indicates the number rows removed due to security constraints. The usual cause is that each row of a list report is first compared against any read access control lists (ACLs) defined on the report's source tables. The ACL is considered for each list row that might be displayed in a report. For more information, see [Report_view access control](https://www.servicenow.com/docs/K6zp1VxfmnOi140a9Qzscw "The report_view operation is a record type ACL that restricts access to data visualizations and Core UI reports. Only users who have one of the required roles can view visualizations that contain the restricted resource."). ## Non-list reports show incomplete data {#report-permission-issues__section_scd_pyn_1vb} Graphical reports (defined as any non-list type report) may show an incomplete set of data for one user, as compared to another user reviewing that same report. This issue is caused by the fact that Before Query business rules are performed on the data from the source table before a report is generated and rendered. Business rules, found on a report's source tables, limit the data based on permissions or similar criteria. Any records that don't fulfill the rule's criteria aren't included in the report. Therefore, users with differing permission levels (due to group or role permissions mainly) see the same report showing different results. For more information, see [Before Query business rules](https://www.servicenow.com/docs/access?context=bp-before-query-business-rules&version=australia&pubname=australia-platform-security&ft:locale=en-US). ## Reports no longer public {#report-permission-issues__section_lxp_3sy_4hc} On upgrade to Australia, all public Core UI reports are unpublished to enhance security awareness and control. The glide.report.published_reports.enabled property on all Core UI reports is set to false. Users with the report_admin role can navigate to the Reports Public \[sys_report_public\] table to view unpublished reports. Such users can also enable the public capacity or enable sharing with logged in users inside the platform. Note: To make a Core UI report available only to users who are logged in, set its Sharing setting to Everyone, but do not publish it.