# Build anonymity rules for metrics

**URL:** <https://visier.discourse.group/t/build-anonymity-rules-for-metrics/304>\
**Category:** Analysis and Visualization\
**Created:** [June 26, 2024, 4:26pm UTC](https://visier.discourse.group/t/build-anonymity-rules-for-metrics/304 "2024-06-26T16:26:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sharan2795](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@Sharan2795](https://visier.discourse.group/u/Sharan2795)\
**Post date:** [June 26, 2024, 4:26pm UTC](https://visier.discourse.group/t/build-anonymity-rules-for-metrics/304/1 "2024-06-26T16:26:51Z")

</div>

Hi There!

Is there a way to not show employee level data for certain metrics in visualizations?

For context, we are experimenting with uploading engagement data into visier from our employee engagement application. One of the main features in our application is to run anonymous surveys which would mean the user who is looking at the survey results would not be able to view data at an employee level, for example, users looking at survey results will not be able to view the answers given by each participant and the engagement score of each participant, they can only view the overall engagement score of the survey if the survey is anonymous.

Below is an example which might help understand the problem better, We have uploaded a sample survey data is Visier and have created a metric called favorability (our version of an engagement score). in the visualization, you can see that we are able to see the favorability at an employee level (by breaking down favorability using employee full names).

 ![image](https://canada1.discourse-cdn.com/flex035/uploads/visier/original/1X/2e6da5ebeb0305cfad2d2b3aa4a71be69e4ded64.png)

In case this was an anonymous survey, we would not want any user to be able to view favorability at an employee level. It’d be great if anyone can help with any solutions for this!

Note: we do pass the information if the survey is anonymous or not as part of the data that comes into Visier.

Thanks,  
Sharan

---

<div class="post-metadata">

**Author:** ![vincent.chu.visier](https://avatars.discourse-cdn.com/v4/letter/v/e95f7d/32.png) [@vincent.chu.visier](https://visier.discourse.group/u/vincent.chu.visier)\
**Post date:** [June 28, 2024, 12:04am UTC](https://visier.discourse.group/t/build-anonymity-rules-for-metrics/304/2 "2024-06-28T00:04:13Z")

</div>

Hi Sharan2795,

Visier supports the scenario you’re describing.  
What you’re describing is known as Aggregate access vs Detailed access in Visier.

Please take a look at:

> **[Data Access Sets](https://docs.visier.com/developer/Studio/permissions/data%20security/data%20access%20sets.htm)**
>
> Data access sets determine the data of the analytic object that can be accessed.

> **[Principles of security](https://study.visier.com/principles-of-visier-security)**
>
> Set up security for Visier users

The resources above should help guide you set it up.

---

<div class="post-metadata">

**Author:** ![burke.lougheed](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@burke.lougheed](https://visier.discourse.group/u/burke.lougheed)\
**Post date:** [June 28, 2024, 3:15pm UTC](https://visier.discourse.group/t/build-anonymity-rules-for-metrics/304/3 "2024-06-28T15:15:49Z")

</div>

In addition to what Vincent has shared on security, you can also leverage Aggregate Thresholds to block values being shown when a population is considered too small/sensitive.

> **[Set Aggregate Thresholds](https://docs.visier.com/embedded/Studio/solution%20settings/aggregate-thresholds-set.htm?Highlight=aggregate%20thresholds)**
>
> Hide aggregate values for small populations from users.