Giving access to Platform Analytics to non-admin users

kim-lindgren
Kilo Sage

Hi,

 

I am trying to give Platform Analytics access to a user that is already working with dashboards a lot in the old interface.

 

I have given him the role 'platform_analytics_admin' just to test and it doesn't change anything. He can see the Platform Analytics modules but cannot open any of them, when he does he invariably gets the message "403: You do not have permissions to access this page."

 

The role 'platform_analytics_admin' should give him access to everything, so I don't see what could be wrong here?

 

Funny thing: I tried opening all Platform Analytics pages in a new tab, but if I open them normally the slug is shortened to 'platform-analytics-workspace' and I don't even get the 403 error message, just an image with a cog wheel saying "Page not found".

 

I realize the problem may be instance-specific but I'm hoping that someone else has encountered a similar problem.

 

Regards,

Kim

12 REPLIES 12

@SusanWinKY 

 

In response to my own question: I talked to the guy who solved it and our problem was not OOB, it was due to a customization.

 

You could look into ACL's related to Platform Analytics Workspace and see if you have any customizations there. Good luck!

@kim-lindgren It turned out to be a customized ACL. After we reverted, all is well. Thanks for pointing me in the right direction!


Susan Williams, Lexmark

spike
Mega Sage

Appreciate this turned out to be a customisation, but can you tell me what that customisation was? I've got the same problem, but can't see anything in the ACLs we've got that would impact it. Of all the new and customised ACLs all ours are against specific tables and their records (incident, change_request etc).

 

Any pointers you could pass me would be most appreciated..

In our case, it was now.platform-analytics-workspace

 

Best,

Kim

For us, it's now.platform-analytics-workspace.* (Type = ux_route, Operation = read) that is in the Platform Analytics application scope (sys_id = 8cc73d60537101100834ddeeff7b128a). We had updated that one for Requires role = admin and have temporarily changed that to Requires role = itil until we officially migrate to Platform Analytics, then we'll revert it to Requires role = snc_internal.

 

By the way, we have a similar ACL in the Discovery Admin Workspace scope that has the discovery_admin role. We've not touched that one.


Susan Williams, Lexmark