Privacy considerations for Viva Insights

Microsoft Viva Insights admins need to consider the following while deciding what privacy settings to use in the different Viva Insights apps.

Minimum group size

A minimum group size helps maintain employee privacy by ensuring that people cannot be easily identified through group attributes. The default minimum group size is five.

The rule

The minimum-group setting determines what you can view in Explore the stats and in Plans. You can change the minimum group size to a level that's more relevant for your organization, but you cannot set the group size to lower than five. The minimum-group-size rule protects people from being individually identified with de-identified data presented in a chart.

Example

The blue-green columns in the following chart represent groups whose size exceeds the minimum group size. For this reason, they display real data.

The gray and white columns on the right represent no data because the groups are below the minimum-group-size threshold.

Histogram charts are an exception to the rule

For histogram charts, the minimum-group-size rule is applied differently, in the following ways:

1. Filter group too small, then no histogram will appear

   If the filter group is below minimum group size that the histogram uses for its data, the histogram will not show any data.

2. Bin population too small, the bin will still appear

   In histograms, the x-axis consists of rectangles (called "bins") that are based on average metric values. The y-axis determines the number of people whose average metric value puts them in that bin. Neither of these values reflects HR data. For this reason, the histogram still displays data for a bin even if it contains fewer people than the minimum-group value. Histogram charts can safely display this information because it is based on metrics -- on values calculated from observed behavior, not on HR data.

   Even if a bin in a histogram contained data for only one individual, the histogram still displays that data. You cannot single out this individual because you do not know what HR “group” they belong to. (In other charts, such as column charts, an individual in a group below the threshold might be identifiable, but in a histogram the HR group to which individuals belong is the larger filter group.) You also cannot determine the precise metric value of an individual because they are in a bin with a minimum 0.5-hour range.

Where to find histogram charts

You can see histogram charts in the following pages in Viva Insights:

• On the Management and coaching page
• For goal setting in Plans
• To track program success on the Track page in Plans

Hash subject lines

You can help maintain employee privacy by hiding the subject lines of meetings and emails. There are privacy and data analysis trade-offs for each scenario. The following information can help you determine whether or not you want to hide subject lines in your queries.

When you select Yes for Hash subject lines, the subject lines are changed to hashed values (a system-generated number), so the text in subject lines will not be readable in any queries.

If you choose to hash subject lines, you can filter query data based on keywords in the subject lines. However, you are not able to see a list of meetings that show the subject lines.

Example: Hashed subject lines

With Hash subject lines turned on, you can run a meeting query with the subject-line keyword “All-hands,” and (based on the attributes you include in the query) it could show data about the number of meetings, the length of meetings, the size of meetings, and so on, with that subject line.

However, you could not get a specific list (one line item for each meeting) of all the meetings with the subject line “All-hands.”

Exclude calendar and email terms from analysis

You can help maintain employee privacy and focus your analysis by excluding certain terms from analysis. Since any items you exclude will not be included in the analysis, it is important to consider and balance your privacy and data analysis goals. It could adversely skew your analysis if you exclude domains, email addresses, or subject terms that frequently appear within the collaboration data set.

The following information can help you determine what privacy settings best match your company’s policies and objectives.

Domains

You can enter a list of domains that you want to exclude. All email, meetings, calls, and instant messages from domains listed here are excluded from analysis.

Email addresses

You can enter a list of email addresses to exclude. Any and all emails and meetings in which these email addresses are included (as both sender/recipient and attendee/invitee) are excluded from analysis. When adding email addresses to exclude, it's important to consider all the sender/recipient and attendee/invitee implications of an exclusion.

Example: Exclude email addresses

If you exclude the email address of the CEO ([email protected]), all meetings and emails in which the CEO is included is removed from analysis. This means that all meetings and emails that include the CEO, the metadata for all other recipients and attendees included in those same emails and meetings are also excluded.

Terms in subject line

You can enter a list of keywords or terms that occur in the subject lines of emails and meetings that you want to exclude. All email and meetings that contain these keywords are excluded from analysis.

Example: Exclude terms from subject line

To exclude all emails with the keywords of “confidential,” “ACP,” and “privileged,” enter: confidential;ACP;privileged

Keyword exclusion logic

• Case is ignored, so you can use upper or lower-case keywords
• Matches exact string match for subject keywords
• Does not match partial words, so you need to list each partial word as a separate term

Examples: Keyword exclusion logic

Related topics

• Privacy and data access