Updating Report Owner / Creator

Scott Jordheim
Giga Guru

Hello, if something happens where I need to update the report owner / creator, how would I go about doing this?

My end goal is changing who has overall rights to the report outside of report_admin or admin. The new report owner would have the report show up in their "My Reports" and be able to edit / save edits as if they just made the report today.

What was mentioned in previous Community posts was changing the User field on the report, but as others mentioned, this will only change who the report is shared with, not who can actually edit it.

I noticed the created_by_user field, but it is currently read-only on the list level. The UI Policy to make reporting fields read-only doens't mention this particular field. If I try to change it from the report's file properties, nothing really seems to happen either.

9 REPLIES 9

Shane J
Tera Guru

Check the List Control on the Report list, it seems to have editing turned off OOTB.

 

Thanks! I'm hoping I can get around having to go this far. If this is needed, I may just have to add that field to the report form itself (the form viewed from the sys_reports table, not the whole creation process wizard), and go from there with ACLs and whatnot.

Michael Ritchie
ServiceNow Employee
ServiceNow Employee

Scott, looking at the ACLs is the best way to determine this.  The out of the box ACL that governs this is this one:

https://INSTANCENAME.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=8fe36cefc0a80165000e52530a8763d7

It is a write ACL on the sys_report table and a script derives if the logged in user is able to update it or not.  To break down the script, here is who has access to update it:

  • By default no users have write access
  • It checks the report's created_by_user and user values to see if there is a match with the logged in user
  • Users with report_admin have access
  • If the report is a Global report, users with the report_global role have access
  • Then it checks the groups access and if the user is a member of one of those groups then access is granted

 

Hope this helps!

This does partially resolves our issue. It addresses the person leaving the company problem for sure. Now I will just have to worry about having to remove access from users to edit their reports when situations arise (and it takes less resources to simply change the report owner Vs update any areas using this report).

I'm really glad you made me aware of this specific ACL, as it brought to light something I didn't even know might be an issue. The fact that report_group and report_global can edit reports shared with them as well as share the reports with said users.

The description on those roles didn't make this point all that clear, and I never thought to dig more into it. It will definitely need to be taken into consideration anytime we give out these roles in the future.