Report security

This blog will probably be a mishmash of Workday, PeopleSoft and SuccessFactors for the foreseeable future as I continue to consult on Workday topics while using SuccessFactors and PeopleSoft in my day to day job.

SuccessFactors

Today, I was supporting an HR user who needed access to certain data in order to do some analysis for the HR VP over here in Europe. I know that I have access to a really good report but my user did not. My user has access to similar data so I asked my SF guru colleague in the US what I needed to do to enable the report for the user.

"Hold on, I'll add her to the report."

Me: Wait, what? We need to grant access to reports individually?

My colleague: "Well, in some cases, yes. It depends how the report security was originally set up."

It's an interesting concept that you can roll out reports and lock them down individually, at a user level but there is always a maintenance and upkeep tradeoff, isn't there?

Workday

I previously posted about Workday domain security and the same concept still holds true. If you can access the domain you can see the data on the pages or in a report.

I guess this SF concept is a little like the 'report sharing' feature in WD. You can share a report with another user which is like giving them the framework and structure to easily run a report but the output is still dependent upon their domain security so you cannot give them more access than what is in the domain security.

PeopleSoft

Old faithful is predictable on the topic of report security. If you have access to all the tables, you can access the report. Even PS had a 'sharing' option but it was more than you were copying your report definition over to another user id and then you each had your own copy rather than a 'shared' version.

So I guess in this case we are more alike than different from a user perspective.  :-)