Idea Exchange: Ability to Change Report Owner | Community
Skip to main content
Level 9
January 29, 2020
Question

Idea Exchange: Ability to Change Report Owner

  • January 29, 2020
  • 11 replies
  • 2054 views
Greetings, Global Community ~ Please consider upvoting this important option within Workfront. Allowing Admins to change report/dashboard ownership is important. Some of you may have already gone through this process of changing report owners and the time it takes to copy, rebuild, reshare... Thank you! Susan
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

11 replies

Level 10
January 30, 2020
Link so we can upvote? Kevin Quosig
Community Advisor
January 30, 2020
I found this idea: Ability to re-assign Ownership of Reports. - I think that's the one :) Sheri Whitten
SusanPfAuthor
Level 9
January 30, 2020
Here's the link. Odd, yesterday it had over 3,000 points. https://experience.workfront.com/s/idea/0870z000000PS8zAAG/detail Susan
SusanPfAuthor
Level 9
January 30, 2020
Here's another. changing Report Owner: https://experience.workfront.com/s/idea/0870z000000PS8zAAG/detail Susan
Level 7
January 30, 2020
There's been an official response, just not the one we want... "Status Update Updated On 2019-05-31 Hi everyone, Thanks for upvoting this idea! However, I'm marking this as "Not Planned", as it is not on our roadmap for the coming 12 months. Thanks, Gevorg Kazaryan" Anthony Pernice
SusanPfAuthor
Level 9
January 30, 2020
My mistake on number of votes. It was another report request different than changing report owner. Susan
Doug_Den_Hoed_AtAppStore
Community Advisor
Community Advisor
January 30, 2020
Hi Anthony, I investigated the API (PortalSection, for those interested) and can understand Gevorg's response: contrary to the owner of (say) an Hour, which can be set to a particular person, the owner of a report appears to be the Entered By field, so -- even for good reason -- changing the entered by for the sake of changing ownership would break several audit trail speed limits. Regards, Doug Doug Den Hoed - AtAppStore
Level 7
January 30, 2020
Given that context, that certainly makes a lot of sense. Perhaps that's something they could add at some point, in the same way projects track both an "owner" as well as (separately) who created it in the first place. Anthony Pernice
SusanPfAuthor
Level 9
January 30, 2020
We don't keep original reports by original owners who leave the company. When user leaves their account is deactivated and the report needs to be copied over to the replacement. It's not a good practice to keep hundreds of reports just because someone left the company and keep them owner. Reports can be recreated and data not altered as it pulls from projects anyway. Susan
Level 10
January 30, 2020
So questions for others who have hit this: Most of our forms were created by WF SysAdmins; three people. What happens to those reports when the original owner leaves? Does it make any difference as long as they were shared out and because SysAdmins can access everything anyway? Same goes for reports created by our original WF Implementation Specialist (i.e., WF employee)...we have deactivated her account, and *I* can access her reports just fine, share them out, but it's really odd having her owner of reports for perpetuity. Our general policy is if a form is to be distributed outside one or two people, users should have SysAdmin create the form (or we take ownership by turning-off their manage access to it) so we can have ongoing management of it. We don't support user-created forms beyond "feel free to tinker, but if we make a system/policy/calculation change, we won't be checking it against anything but forms we directly manage." This is mostly due to the fact that we have limited man-hours to devote to WF administration. We have to keep to a centralized model to reign-in the chaos. However, I do wish too that I could "change owners" or as someone else put it: separate "creator" from "manager/owner" of a report. Things like reports should have the ability to make them "owned by the system, not a specific user." Kevin Quosig