Report integrity when owner is deactivated - to "Run As" or not?

[-JC]

Hello, I'm hoping someone can clarify for me whether or not it is required to set a new user in the "Run As" field of a report when the creator of that report is being deactivated. In testing, it seems to be #2, but I want to make sure I'm not missing anything.

1) If a report is created by a user being deactivated but the "Run As" field is blank, that report must be set up with a "Run As" of an active user in order to continue functioning

-or-

2) If a report is created and the "Run As" field is set to a a user who is being deactivated, that report must be set up with a "Run As" of an active user in order to continue functioning

[KellieGWAB · Accepted solution]

Hi Jaye - you only need to setup a new "run as" if there is something in the field currently. If it's blank it can be left blank. Just because the user created the report doesn't mean it has any bearing on the report functionality. Only the run as or filters indicating that user would impact the report functionality. 

If the report is set to "run as" the user you are deactivating you'll want to change it to a different user that has the same kind of permissions as the departing user. 

[-JC]

Many thanks @KellieGWAB, appreciate it!

[KellieGWAB]

No problem.

Speaking from experience, I now try to sway my users from running reports with "run as" populated with anything unless they are a system admin. And to evaluate the true need for it before setting it up. I had a group admin who did this with every report he created and when he left, I had 500 reports (that's another problem, haha) that I had to manually edit to remove him from.

[-JC]

Super fair!! The user I'm deactivating IS a system admin, so it makes sense in this scenario, but even for myself as a core admin it's worth considering cleaning up my own "Run As" reports. 500 reports - that's a darn shame!! Job security? Haha. Thanks again!