Controlling who has access to survey results

[Mprov113]

I'm having a hard time managing who can and cannot see assessments and survey results.    

If I give a user survey_reader role they can see all surveys but can't see any reports and dashboards.

If I give them survey_user role they can see everyone's responses for every assessment and survey.  

Question: 

How do I create assessments for different users and give those users full access to those surveys/assessments BUT not have any access to other users' surveys/assessments and results???  

If it is an ACL setting, please explain because I can't seem to find the right solution here.  I'm currently using Tokyo.  

Thank you all in advance!! 

Mike 

[Allen Andreas · Accepted solution]

Hi,

Not sure if you may have posted this question on the forums recently (perhaps under another account)? As this is very similar to one just posted, haha. In any case, yes, it would be a combination of ACLs where you'd have to adjust what those roles do within your instance or...create custom and add ACLs (which would be my suggestion - so that you're not changing what the survey_reader and survey_user roles mean in your instance).

You'd want to create a custom role and name it whatever you'd like, then create a "read" ACL on the table "asmt_metric_result". That is where the results are stored. Then, you'd need to add a condition to that ACL such as "assignment group" is DYNAMIC "one of my groups"...this is just an example, but the point here is that you need to tell the ACL HOW to filter what they can see. You'd have to figure that part out as to how those surveys are specific to certain people or groups.

[Allen Andreas]

Hi,

Thanks for marking my above reply as Helpful.

If it also helped guide you correctly, please also mark it as "Accept Solution".

Thanks and take care! 🙂

[Matt Small1]

This information is helpful in setting up an ACL but how come Service Now has not set this up to be a configuration on the Assessment/Survey Metric definition table .  It would be be able to define a group and/or list of users that have access to view that particular metric results.  The option of needing to create an ACL may need to be done for each Metric definition that gets created.  That is a lot of overhead.