Is it Possible to restrict the list of tables that appear in the reporting tables in the Reporting Module

kagarwni
Kilo Expert

We are trying to restrict reporting for a user to limited tables .

The 2 solutions could be :

1. Hiding the tables to appear from the reporting list

2. Ensuring that no data appears eventhough the not-needed table is selected.

Also, am trying to understand difference between an ACL on sys_report and report_view.

Any leads regarding this will help a lot.

Release : Eureka

Regards

Nitin

1 ACCEPTED SOLUTION

Just chiming in to help clarify.   "report_on" isn't a role, it's an ACL operation (like create, read, write, delete).


You will only need an explicit report_on ACL for tables on which you wish to CREATE new reports.


You can modify an existing report, and users will be able to see all tables on which they have READ access.


Per the wiki:


  • Users can still run published (global) reports against tables for which they have read rights, even if they cannot create reports.
  • System tables are not reportable by default. To allow reporting against system tables, administrators can configure the glide.ui.permitted_tables property. To learn more, see Reporting on System Tables.
  • The default ACL report_on operation gives access to report on the target table, any associated database view, and archived version of the target table.


OOB ITIL users can create reports on an enormous number of tables.   You can restrict these by adding a report_on ACL that provides a test condition (say a custom role) that fails.   If there's a specific table that you're seeing that you don't think you should, let us know what it is and we should be able to help you figure out why it's showing up.


View solution in original post

11 REPLIES 11

Just chiming in to help clarify.   "report_on" isn't a role, it's an ACL operation (like create, read, write, delete).


You will only need an explicit report_on ACL for tables on which you wish to CREATE new reports.


You can modify an existing report, and users will be able to see all tables on which they have READ access.


Per the wiki:


  • Users can still run published (global) reports against tables for which they have read rights, even if they cannot create reports.
  • System tables are not reportable by default. To allow reporting against system tables, administrators can configure the glide.ui.permitted_tables property. To learn more, see Reporting on System Tables.
  • The default ACL report_on operation gives access to report on the target table, any associated database view, and archived version of the target table.


OOB ITIL users can create reports on an enormous number of tables.   You can restrict these by adding a report_on ACL that provides a test condition (say a custom role) that fails.   If there's a specific table that you're seeing that you don't think you should, let us know what it is and we should be able to help you figure out why it's showing up.


I followed your response as to how to remove a table from displaying in the report module however the table entry still displays.     The ACL report_on is inactive for the table that I do not want displayed.   Any suggestions


robpickering
ServiceNow Employee
ServiceNow Employee

Jerry,



It's a little difficult to understand.   By default, you have the ability to Report On any table to which you have Read access, other than System tables.


If you wish to restrict those tables, you'll have to put a report_on ACL on the table and DENY access to it for the group you wish to restrict.  



-Rob


kagarwni
Kilo Expert

Thanks Robert and Tom for your valuable inputs.


Much appreciated !


Jerry20
Tera Contributor

By making the report_on ACL inactive I would think this would remove it form the list as we do not want anyone to access this anymore.   There are no roles associated with this report_on