From f1e0b0bfa1eed2783e5771bdd5316bb6abf6f2b5 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 10:50:23 -0400 Subject: [PATCH 01/20] Create privacy-360-feedback.md --- Viva/glint/setup/privacy-360-feedback.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 Viva/glint/setup/privacy-360-feedback.md diff --git a/Viva/glint/setup/privacy-360-feedback.md b/Viva/glint/setup/privacy-360-feedback.md new file mode 100644 index 000000000..da56c5a70 --- /dev/null +++ b/Viva/glint/setup/privacy-360-feedback.md @@ -0,0 +1,21 @@ +--- +title: Privacy protection within for 360 feedback programs +description: +ms.author: JudithWeiner +author: JudyWeiner +manager: MelissaBarry +audience: admin +ms.collection: +- essentials-privacy +f1.keywords: NOCSH +keywords: Thresholds, suppression, response rate, suppressed data, identifiable surveys + - m365initiative-viva + - selfserve +search-appverid: MET150 +ms.topic: concept-article +ms.service: viva-glint +ms.localizationpriority: high +ms.date: 10/07/2024 +--- + +# Privacy protection for 360 feedback programs From d738135fb362728b7be931af0c24e7f27eac056d Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 10:50:33 -0400 Subject: [PATCH 02/20] Create privacy-protection-reporting.md --- .../setup/privacy-protection-reporting.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 Viva/glint/setup/privacy-protection-reporting.md diff --git a/Viva/glint/setup/privacy-protection-reporting.md b/Viva/glint/setup/privacy-protection-reporting.md new file mode 100644 index 000000000..0e2d2287d --- /dev/null +++ b/Viva/glint/setup/privacy-protection-reporting.md @@ -0,0 +1,21 @@ +--- +title: Privacy protection within feedback reporting +description: +ms.author: JudithWeiner +author: JudyWeiner +manager: MelissaBarry +audience: admin +ms.collection: +- essentials-privacy +f1.keywords: NOCSH +keywords: Thresholds, suppression, response rate, suppressed data, identifiable surveys + - m365initiative-viva + - selfserve +search-appverid: MET150 +ms.topic: concept-article +ms.service: viva-glint +ms.localizationpriority: high +ms.date: 10/07/2024 +--- + +# Privacy protection within feedback reporting From 53f7637dec47d62a044eeecb47c5f143857a32a2 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 10:50:42 -0400 Subject: [PATCH 03/20] Update viva-glint-survey-privacy.md --- Viva/glint/setup/viva-glint-survey-privacy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Viva/glint/setup/viva-glint-survey-privacy.md b/Viva/glint/setup/viva-glint-survey-privacy.md index f5bd70a2e..cf6fe5bf7 100644 --- a/Viva/glint/setup/viva-glint-survey-privacy.md +++ b/Viva/glint/setup/viva-glint-survey-privacy.md @@ -15,14 +15,14 @@ search-appverid: MET150 ms.topic: concept-article ms.service: viva-glint ms.localizationpriority: high -ms.date: 09/11/2024 +ms.date: 10/07/2024 --- # How Viva Glint helps protect your privacy Data privacy and trust are key priorities for Microsoft Viva Glint. Individual privacy is a core Viva Glint value. When survey respondents feel confident that their privacy is protected, they're more likely to participate in surveys and provide honest and constructive feedback. This is how our customers get the most out of Glint. -Glint uses several methods to inform you about what level of privacy users can expect when responding, starting with the survey type. Glint offers two types of surveys: confidential and identifiable. +Glint uses several methods to inform about what level of privacy users can expect when responding, starting with the survey type. Glint offers two types of surveys: confidential and identifiable. ## Confidential surveys From e51287db3c57cd3568265e0da3d13649673766b2 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 10:52:52 -0400 Subject: [PATCH 04/20] Update viva-glint-survey-privacy.md --- Viva/glint/setup/viva-glint-survey-privacy.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/Viva/glint/setup/viva-glint-survey-privacy.md b/Viva/glint/setup/viva-glint-survey-privacy.md index cf6fe5bf7..97e11f5d6 100644 --- a/Viva/glint/setup/viva-glint-survey-privacy.md +++ b/Viva/glint/setup/viva-glint-survey-privacy.md @@ -138,16 +138,6 @@ In some cases, even when the minimum response threshold is met, the ability to f > > For the North American score to be displayed, there must be more than two (2) responses within the overall team score that aren't within the North American group. So, if the overall team earned eight (8) responses where five (5) were from North America and three (3) were from Europe, the PM sees both the overall team score and the North American score. The, suppression threshold was met. -## 360 feedback programs - -The confidentiality statement displayed for 360 feedback participants depends on the type of feedback provider, the selected confidentiality threshold, and the Feedback Provider Response Information setting in a 360 feedback cycle. Review this information to see the statement that displays for each user in each situation. - -|Feedback provider |Confidentiality threshold |Feedback provider response information setting |Confidentiality statement| -|:----------|:-----------|:------------|:------------| -|Self |1 |On or Off |Your feedback is visible to you and a limited number of people that are granted permission by your organization to view your 360 report. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | -|**Non-subject**: Manager, Skip-level manager, or Custom |1 |On or Off |Note that this is an identifiable survey, which means Contoso will be able to see that your survey responses came from you. Whether you responded, as well as your feedback, will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | -|**Non-subject**: Directs, Peers, Colleagues, or Custom |3 or more |Off |Your responses are confidential and reported to Contoso in aggregate groups of 3 or more respondents, including any write-in comments which are reported verbatim. Take care not to identify yourself in the comments. Your aggregated feedback will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md), which describes other ways your data may be accessed, and your organization's Privacy Policy for more information. | -|**Non-subject**: Directs, Peers, Colleagues, or Custom |3 or more |On |Your responses are confidential and reported to Contoso in aggregate groups of 3 or more respondents, including any write-in comments which are reported verbatim. Take care not to identify yourself in the comments. Whether you responded, as well as your aggregated feedback, will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md), which describes other ways your data may be accessed, and your organization's Privacy Policy for more information. | > [!IMPORTANT] > - "Contoso" and confidentiality thresholds in statements pull in your organization's name and threshold information. From 19df28b8f72583556ff0035936bf72f78f01e392 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 10:52:59 -0400 Subject: [PATCH 05/20] Update privacy-360-feedback.md --- Viva/glint/setup/privacy-360-feedback.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/Viva/glint/setup/privacy-360-feedback.md b/Viva/glint/setup/privacy-360-feedback.md index da56c5a70..843f9f989 100644 --- a/Viva/glint/setup/privacy-360-feedback.md +++ b/Viva/glint/setup/privacy-360-feedback.md @@ -19,3 +19,19 @@ ms.date: 10/07/2024 --- # Privacy protection for 360 feedback programs + +## 360 feedback programs + +The confidentiality statement displayed for 360 feedback participants depends on the type of feedback provider, the selected confidentiality threshold, and the Feedback Provider Response Information setting in a 360 feedback cycle. Review this information to see the statement that displays for each user in each situation. + +|Feedback provider |Confidentiality threshold |Feedback provider response information setting |Confidentiality statement| +|:----------|:-----------|:------------|:------------| +|Self |1 |On or Off |Your feedback is visible to you and a limited number of people that are granted permission by your organization to view your 360 report. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | +|**Non-subject**: Manager, Skip-level manager, or Custom |1 |On or Off |Note that this is an identifiable survey, which means Contoso will be able to see that your survey responses came from you. Whether you responded, as well as your feedback, will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | +|**Non-subject**: Directs, Peers, Colleagues, or Custom |3 or more |Off |Your responses are confidential and reported to Contoso in aggregate groups of 3 or more respondents, including any write-in comments which are reported verbatim. Take care not to identify yourself in the comments. Your aggregated feedback will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md), which describes other ways your data may be accessed, and your organization's Privacy Policy for more information. | +|**Non-subject**: Directs, Peers, Colleagues, or Custom |3 or more |On |Your responses are confidential and reported to Contoso in aggregate groups of 3 or more respondents, including any write-in comments which are reported verbatim. Take care not to identify yourself in the comments. Whether you responded, as well as your aggregated feedback, will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md), which describes other ways your data may be accessed, and your organization's Privacy Policy for more information. | + +> [!IMPORTANT] +> - "Contoso" and confidentiality thresholds in statements pull in your organization's name and threshold information. +> - The phrase "Privacy Policy" in each statement becomes a hyperlink to your organization's policy when a link is added in General Settings. [Learn more](https://go.microsoft.com/fwlink/?linkid=2272862). + From ca66195567ec3781fac413e39c5da42c49719361 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 11:02:19 -0400 Subject: [PATCH 06/20] Update viva-glint-survey-privacy.md --- Viva/glint/setup/viva-glint-survey-privacy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Viva/glint/setup/viva-glint-survey-privacy.md b/Viva/glint/setup/viva-glint-survey-privacy.md index 97e11f5d6..d4159bd26 100644 --- a/Viva/glint/setup/viva-glint-survey-privacy.md +++ b/Viva/glint/setup/viva-glint-survey-privacy.md @@ -1,5 +1,5 @@ --- -title: How Viva Glint helps protect your privacy +title: How Viva Glint protects your privacy description: Data privacy and trust are key priorities, and Viva Glint is constantly evolving ways to protect confidentiality to encourage elevated levels of survey participation and honest and helpful feedback. ms.author: JudithWeiner author: JudyWeiner @@ -18,7 +18,7 @@ ms.localizationpriority: high ms.date: 10/07/2024 --- -# How Viva Glint helps protect your privacy +# How Viva Glint protects your privacy Data privacy and trust are key priorities for Microsoft Viva Glint. Individual privacy is a core Viva Glint value. When survey respondents feel confident that their privacy is protected, they're more likely to participate in surveys and provide honest and constructive feedback. This is how our customers get the most out of Glint. From 0a33c665f1a06b22080b20937f8396d41353fc5e Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 11:05:04 -0400 Subject: [PATCH 07/20] Update TOC.yml --- Viva/glint/TOC.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/Viva/glint/TOC.yml b/Viva/glint/TOC.yml index 2612093c1..654db5111 100644 --- a/Viva/glint/TOC.yml +++ b/Viva/glint/TOC.yml @@ -10,7 +10,13 @@ items: - name: Confidentiality versus anonymity href: setup/anonymous-confidential.md - name: Privacy protection - href: setup/viva-glint-survey-privacy.md + items: + - name: How Viva Glint protects your privacy + href: setup/viva-glint-survey-privacy.md + - name: Privacy protection within feedback reporting + href: setup/privacy-protection-reporting.md + - name: Privacy protection for 360 feedback programs + href: setup/privacy-360-feedback.md - name: Raw response data href: setup/employee-raw-data-export.md - name: Connect and learn From a884ef5e0c76eab8fa6425e49d6433a5ee1ef557 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 13:42:35 -0400 Subject: [PATCH 08/20] Update privacy-360-feedback.md --- Viva/glint/setup/privacy-360-feedback.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/Viva/glint/setup/privacy-360-feedback.md b/Viva/glint/setup/privacy-360-feedback.md index 843f9f989..d61ac3f8b 100644 --- a/Viva/glint/setup/privacy-360-feedback.md +++ b/Viva/glint/setup/privacy-360-feedback.md @@ -1,6 +1,6 @@ --- -title: Privacy protection within for 360 feedback programs -description: +title: Privacy protection within 360 feedback programs +description: The confidentiality statement displayed for 360 feedback participants depends on the type of feedback provider, the confidentiality threshold, and the Feedback Provider Response Information setting. ms.author: JudithWeiner author: JudyWeiner manager: MelissaBarry @@ -8,7 +8,7 @@ audience: admin ms.collection: - essentials-privacy f1.keywords: NOCSH -keywords: Thresholds, suppression, response rate, suppressed data, identifiable surveys +keywords: Thresholds, suppression, response rate, suppressed data, - m365initiative-viva - selfserve search-appverid: MET150 @@ -18,12 +18,17 @@ ms.localizationpriority: high ms.date: 10/07/2024 --- -# Privacy protection for 360 feedback programs +# Privacy protection 360 feedback programs ## 360 feedback programs The confidentiality statement displayed for 360 feedback participants depends on the type of feedback provider, the selected confidentiality threshold, and the Feedback Provider Response Information setting in a 360 feedback cycle. Review this information to see the statement that displays for each user in each situation. +> [!IMPORTANT] +> Thresholds can't be lowered or raised for programs or cycles after it's launched. + +https://learn.microsoft.com/en-us/viva/glint/setup/viva-glint-survey-privacy + |Feedback provider |Confidentiality threshold |Feedback provider response information setting |Confidentiality statement| |:----------|:-----------|:------------|:------------| |Self |1 |On or Off |Your feedback is visible to you and a limited number of people that are granted permission by your organization to view your 360 report. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | From 20762d546a4ec93378d6aacfb1afa8badd769dde Mon Sep 17 00:00:00 2001 From: zachminers <138257873+zachminers@users.noreply.github.com> Date: Mon, 7 Oct 2024 11:47:56 -0600 Subject: [PATCH 09/20] Copy edits for new note --- Viva/insights/advanced/analyst/query-results.md | 5 ++++- Viva/insights/advanced/reference/metrics.md | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/Viva/insights/advanced/analyst/query-results.md b/Viva/insights/advanced/analyst/query-results.md index c9c34d9bc..bff73a78f 100644 --- a/Viva/insights/advanced/analyst/query-results.md +++ b/Viva/insights/advanced/analyst/query-results.md @@ -1,5 +1,5 @@ --- -ms.date: 07/03/2024 +ms.date: 10/07/2024 title: Access query results and modify existing queries description: Learn how to access query results in the advanced insights app author: zachminers @@ -160,6 +160,9 @@ Deleting a query removes it from the results list for everyone in the organizati When you define a query, you select metrics and employee attributes. After the query runs, its results are organized into columns and rows. The column headers in the results match the attribute names and metric names that you selected while defining the query. To learn how to download these results, read on. +>[!Note] +>"NULL" values in your results indicate employees without a Microsoft 365 Copilot license, which signifies no activity due to the absence of a license. A "0" value, on the other hand, indicates users with a license but who did not engage in any activity for the specified day, week, or month. + #### Downloading and connecting to results ##### Download and import results in Excel diff --git a/Viva/insights/advanced/reference/metrics.md b/Viva/insights/advanced/reference/metrics.md index ed8f1a4c7..fc976ab57 100644 --- a/Viva/insights/advanced/reference/metrics.md +++ b/Viva/insights/advanced/reference/metrics.md @@ -1,5 +1,5 @@ --- -ms.date: 10/4/2024 +ms.date: 10/07/2024 title: Advanced insights metric descriptions description: Describes the metrics for analysis data that are available in Microsoft Viva Insights, including query metrics and Power BI template metrics author: zachminers @@ -190,6 +190,9 @@ When you create queries in the Microsoft Viva Insights advanced insights app, yo These metrics provide insights around how employees are using Microsoft 365 Copilot with Microsoft 365 apps. +>[!Note] +>"NULL" values in your query results indicate employees without a Microsoft 365 Copilot license, which signifies no activity due to the absence of a license. A "0" value, on the other hand, indicates users with a license but who did not engage in any activity for the specified day, week, or month. + | Metric | Description | Date from when the data is available and the customers can view | |---|---|---| | Summarize meeting actions taken using Copilot in Teams | The number of times users summarized meetings using Copilot. Each action represents a user sending a prompt in the meeting Copilot dialog (including suggested prompts and user-generated prompts). This metric does *not* include meeting summaries accessed through Intelligent Recap. | 10/15/2023 | From 566209707f8520a775f51e4d7ecd2b9157d6edc4 Mon Sep 17 00:00:00 2001 From: zachminers <138257873+zachminers@users.noreply.github.com> Date: Mon, 7 Oct 2024 11:52:21 -0600 Subject: [PATCH 10/20] Update metrics.md --- Viva/insights/advanced/reference/metrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Viva/insights/advanced/reference/metrics.md b/Viva/insights/advanced/reference/metrics.md index fc976ab57..9769472d4 100644 --- a/Viva/insights/advanced/reference/metrics.md +++ b/Viva/insights/advanced/reference/metrics.md @@ -191,7 +191,7 @@ When you create queries in the Microsoft Viva Insights advanced insights app, yo These metrics provide insights around how employees are using Microsoft 365 Copilot with Microsoft 365 apps. >[!Note] ->"NULL" values in your query results indicate employees without a Microsoft 365 Copilot license, which signifies no activity due to the absence of a license. A "0" value, on the other hand, indicates users with a license but who did not engage in any activity for the specified day, week, or month. +>"NULL" values in analyst query results indicate employees without a Microsoft 365 Copilot license, which signifies no activity due to the absence of a license. A "0" value, on the other hand, indicates users with a license but who did not engage in any activity for the specified day, week, or month. | Metric | Description | Date from when the data is available and the customers can view | |---|---|---| From 68ccd773372f7266977b12917bfd0c44da11b381 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:07:46 -0400 Subject: [PATCH 11/20] Update viva-glint-survey-privacy.md --- Viva/glint/setup/viva-glint-survey-privacy.md | 105 ++++-------------- 1 file changed, 19 insertions(+), 86 deletions(-) diff --git a/Viva/glint/setup/viva-glint-survey-privacy.md b/Viva/glint/setup/viva-glint-survey-privacy.md index d4159bd26..be92d911d 100644 --- a/Viva/glint/setup/viva-glint-survey-privacy.md +++ b/Viva/glint/setup/viva-glint-survey-privacy.md @@ -1,6 +1,6 @@ --- title: How Viva Glint protects your privacy -description: Data privacy and trust are key priorities, and Viva Glint is constantly evolving ways to protect confidentiality to encourage elevated levels of survey participation and honest and helpful feedback. +description: Viva Glint is constantly evolving ways to protect confidentiality to encourage elevated levels of survey participation and honest and helpful feedback. ms.author: JudithWeiner author: JudyWeiner manager: MelissaBarry @@ -20,33 +20,26 @@ ms.date: 10/07/2024 # How Viva Glint protects your privacy -Data privacy and trust are key priorities for Microsoft Viva Glint. Individual privacy is a core Viva Glint value. When survey respondents feel confident that their privacy is protected, they're more likely to participate in surveys and provide honest and constructive feedback. This is how our customers get the most out of Glint. +Data privacy and trust are key priorities for Microsoft Viva Glint. Individual privacy is a core Viva Glint value. When survey respondents feel confident that their privacy is protected, they're more likely to participate in surveys and provide honest and constructive feedback. This enables you to get the most from your Glint programs. -Glint uses several methods to inform about what level of privacy users can expect when responding, starting with the survey type. Glint offers two types of surveys: confidential and identifiable. +Glint offers two types of surveys: confidential and identifiable. ## Confidential surveys -For confidential surveys, Glint aggregates (group averages) responses before reporting results. It's easier to guess a survey taker's identity when there are just a few responses. For this reason, confidential survey responses are reported only when an item meets the confidentiality threshold for responses. Your organization chooses this number and it might differ for *items* versus *comments*. For a survey to be confidential, the minimum number of responses is three (3). +For confidential surveys, Glint aggregates (group averages) responses before reporting results. It's easier to guess a survey taker's identity when there are just a few responses. For this reason, confidential survey responses are reported *only* when an item meets the confidentiality threshold for responses. Your organization chooses this number and it might differ for *items* versus *comments*. -> [!NOTE] -> Glint surveys might contain three types of items/questions: -> -> - Ratings: Survey takers choose a score on a numerical scale. -> - Multiple choice: Survey takers choose from pre-populated options -> - Comments: Survey takers write in freeform comments. +For a survey to be confidential, the minimum number of responses is three (3). ## Identifiable surveys -In Identifiable surveys, survey takers' identities might be directly or indirectly available within reporting. The minimum response threshold for these surveys is less than three. An example of an identifiable survey could be a company's Exit survey, where viewing responses for each departing employee is necessary. +In Identifiable surveys, survey takers' identities might be directly or indirectly available within reporting. The minimum response threshold for these surveys is *less than three*. An example of an identifiable survey could be a company's Exit survey, where viewing responses for each departing employee is necessary. >[!IMPORTANT] ->Admins can make Glint Lifecycle and Always-On surveys identifiable in **Program Setup, ** in the Confidential Responses setting, which automatically updates thresholds at the survey level. +>Admins can make Glint Employee Lifecycle and Always-On surveys identifiable in **Program Setup,** in the Confidential Responses setting, which automatically updates thresholds at the survey level. ## Use your organization's statement about privacy -At the beginning of each Glint survey, survey takers are presented with a statement configured by your organization. - -**How does a statement about privacy help?** +At the beginning of each Glint survey, survey takers are presented with a privacy statement configured by your organization. A privacy statement provides information about who can see survey takers' identifiable responses and under what circumstances. It specifies whether the survey is confidential or identifiable and the minimum response threshold set by your organization. It also notifies survey takers of any potential admin access to identifiable survey responses and provides links to more Microsoft privacy documentation. Your organization can include a link to its employee privacy policy or other documentation about how it handles survey data. @@ -57,88 +50,28 @@ Even for confidential surveys, your organization's customer admin might be able > [!IMPORTANT] > A statement is automatically selected based on your program setup configurations. -## Confidential survey statement for surveys that *don't* support raw survey responses export +## Confidential survey statement: surveys that *don't* support raw survey responses export If your organization restricts the export of raw survey responses for confidential surveys, this statement is applied to surveys: -> Your responses are confidential and reported to [Organization name] in aggregate groups of 5 or more respondents. Write-in comments are reported verbatim if at least 10 people respond to a question. Take care not to identify yourself in the comments. Microsoft Viva Glint Reporting and Confidentiality Rules describe other ways your data might be accessed and your organization's Privacy Policy also has more information. +> Your responses are confidential and reported to [Organization name] in aggregate groups of 5 or more respondents. Write-in comments are reported verbatim if at least 10 people respond to a question. Take care not to identify yourself in the comments. [Microsoft Viva Glint Reporting and Confidentiality](/viva/glint/reports/confidentiality-suppression-reports) describes other ways your data might be accessed and your organization's privacy policy also has more information. -## Confidential survey statement for surveys that *do* support raw survey responses export +## Confidential survey statement: surveys that *do* support raw survey responses export If your organization approves making raw survey responses available, survey takers are informed in this statement: -> Your responses are confidential and reported to [Organization name] in aggregate groups of 5 or more respondents. Write-in comments are reported verbatim if at least 10 people respond to a question. Take care not to identify yourself in the comments. A limited number of people at [organization name] will have access to your identifiable survey responses. See [Microsoft Viva Glint Reporting and Confidentiality Rules](https://go.microsoft.com/fwlink/?linkid=2230922), which describes other ways your data may be accessed and your organization's privacy policy for more information. - -## Survey statement for identifiable surveys - -If your organization opts to create an identifiable survey, this statement is applied: - -> Note that this is an identifiable survey, which means Contoso will be able to see that your survey responses came from you. See your organization's Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](https://go.microsoft.com/fwlink/?linkid=2230922). - -> [!NOTE] -> The Confidentiality and Comments threshold set for programs automatically becomes the default statement. - -## How is privacy protected within results reporting? - -Survey takers' privacy is protected by setting and communicating a minimum number of responses used in reporting, as well as management of roles and permissions. Your organization configures who has access to survey data and establishes the minimum response thresholds for each survey program. +> Your responses are confidential and reported to [Organization name] in aggregate groups of five or more respondents. Write-in comments are reported verbatim if at least 10 people respond to a question. Take care not to identify yourself in the comments. A limited number of people at [organization name] will have access to your identifiable survey responses. See [Microsoft Viva Glint Reporting and Confidentiality](/viva/glint/reports/confidentiality-suppression-reports), which describes other ways your data may be accessed and your organization's privacy policy. -A minimum response threshold is the lowest number of responses a survey item must receive for its results to be reported. The higher the level of aggregation, the less likely it is that users reviewing a survey report are able to infer the identity of an individual survey taker. +> [!IMPORTANT] +> - "*Contoso*" and *confidentiality thresholds* macros in statements pull in your organization's name and threshold information. +> - The phrase "Privacy Policy" in each statement becomes a hyperlink to your organization's policy when the link is added in [General Settings](/viva/glint/setup/manage-general-settings). - - By default, the minimum response threshold for rating or multiple-choice items is five. - - For comments, the minimum response threshold is 10. +## Survey statement: identifiable surveys -Your organization can adjust the thresholds, higher or lower, for each survey program, and these thresholds are noted to survey takers. +If your organization opts to create an identifiable survey, this statement is applied: -At the beginning of a survey, the privacy statement informs the participants whether the survey is confidential or identifiable and specifies its minimum response thresholds. Once a program is launched, its minimum response thresholds can't be changed. **Changing or altering a minimum response threshold requires a new survey program.** The previous program with the original confidentiality threshold could, however, be drawn into reports for comparison against new results with the new threshold. +> Note that this is an identifiable survey, which means Contoso will be able to see that your survey responses came from you. See your organization's Privacy Policy for more information. Learn how Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality](/viva/glint/reports/confidentiality-suppression-reports). > [!NOTE] -> To be classified as a *confidential* survey, the minimum number of responses is three (3) or higher. If the threshold is below three (3), the survey is *identifiable*. - -## Privacy is protected by managing reporting roles and permissions - -Your organization configures who views and configures survey reports at various levels. For instance, your organization might use the following reporting hierarchy for its marketing organization and assign permissions accordingly: - -1. Marketing program managers (PMs) can only view survey results from the team they manage. -2. Marketing directors (to whom marketing PMs report) can view survey results for all teams reporting up through them. -3. The Chief Marketing Officer (to whom the marketing director reports) can view survey data for the entire marketing organization. - -Each reporting group feeds into a hierarchy level, or rollup, giving users visibility related to their role and authority. +> Confidentiality and Comments thresholds set for programs automatically becomes the default statement. -If the minimum response threshold isn't met for a user's team, their responses aren't reported. Instead, responses are aggregated with and rolled up to the next level. - -> Consider a survey of the marketing organization described above with the minimum reporting threshold set to five (5). A marketing PM can see aggregated survey responses for any item to which at least five (5) of their team members responded. But if only four (4) responded to a specific item, the responses for that item aren't shown to the marketing PM. Instead, the responses are combined with those of other employees reporting up through the marketing director and rolled in to the next reporting level - the marketing director. -> -> The PM won't see survey data for that item because the minimum response threshold wasn't met. As the threshold was met at the reporting level, the survey data is included in the director's report. - -## The comments threshold differs from the survey items threshold - -The default minimum response thresholds for ratings and multiple-choice questions are five (5), but for comments the default threshold is 10. Comments are easier to identify to a respondent. The report user might notice a writing or grammatical style that is unique to a specific person. The smaller the group, the larger the potential to deduce the survey respondent. - -> If a manager receives seven (7) responses from their team, they'll see an aggregated score but not the comments. On the other hand, if a manager receives 20 responses, they'll see the calculated score *and* the comments, regardless of the number of comments received. - -## Suppression thresholds add further protection - -In some cases, even when the minimum response threshold is met, the ability to filter a report by attributes might allow a responder to be identified. In these cases, responses are **suppressed**,— they aren't reported even if the minimum response threshold is met. - ->[!IMPORTANT] ->The suppression threshold requires two (2) or more responses that separate the smallest attribute group from the next smallest group that meets the minimum response threshold. - -**Example - Marketing PM** -> - Five (5) of the six (6) team members are in North America; one (1) is in Europe. -> - The organization configured Glint to allow filtering of responses by survey taker region. -> - The survey's minimum response threshold is five (5). -> - All six (6) team members respond to an item that asks them to rate their manager's communication skills, from 'Very Good' to 'Very Poor.' -> - The North America team members all provide a rating of 'Very Good;' the European team member provide a rating of 'Very Poor.' - ->In this case, the marketing PM can't see the European score because, with only one (1) response from European employees, the minimum response threshold isn't met. But the PM can view the teamwide score (based on six responses) and North American-only score (based on five responses)—right? **No!** Those results are **suppressed**. - ->**Why?** - -> By comparing the teamwide score to the North American score, the PM might mathematically be able to determine the score received from the single European team member. When the PM sees that the North American score is 'Very Good,' but the teamwide score isn't, the user might infer that the European team member brought the average down. With a little math, the PM could calculate the exact score the European team member provided. -> -> For the North American score to be displayed, there must be more than two (2) responses within the overall team score that aren't within the North American group. So, if the overall team earned eight (8) responses where five (5) were from North America and three (3) were from Europe, the PM sees both the overall team score and the North American score. The, suppression threshold was met. - - -> [!IMPORTANT] -> - "Contoso" and confidentiality thresholds in statements pull in your organization's name and threshold information. -> - The phrase "Privacy Policy" in each statement becomes a hyperlink to your organization's policy when a link is added in General Settings. [Learn more](https://go.microsoft.com/fwlink/?linkid=2272862). From 28a51b35e0132dc956394d5f6d050fe6c7843228 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:31:49 -0400 Subject: [PATCH 12/20] Update privacy-protection-reporting.md --- .../setup/privacy-protection-reporting.md | 93 ++++++++++++++++++- 1 file changed, 91 insertions(+), 2 deletions(-) diff --git a/Viva/glint/setup/privacy-protection-reporting.md b/Viva/glint/setup/privacy-protection-reporting.md index 0e2d2287d..0a495ffdd 100644 --- a/Viva/glint/setup/privacy-protection-reporting.md +++ b/Viva/glint/setup/privacy-protection-reporting.md @@ -1,6 +1,6 @@ --- title: Privacy protection within feedback reporting -description: +description: Survey takers' privacy is protected by setting and communicating a minimum number of responses used in reporting, as well as management of roles and permissions. ms.author: JudithWeiner author: JudyWeiner manager: MelissaBarry @@ -8,7 +8,7 @@ audience: admin ms.collection: - essentials-privacy f1.keywords: NOCSH -keywords: Thresholds, suppression, response rate, suppressed data, identifiable surveys +keywords: Thresholds, suppression, response rate, suppressed data, comments threshold, survey items threshold - m365initiative-viva - selfserve search-appverid: MET150 @@ -19,3 +19,92 @@ ms.date: 10/07/2024 --- # Privacy protection within feedback reporting + +Survey takers' privacy is protected by setting and communicating a minimum number of responses used in reporting, as well as management of roles and permissions. Your organization configures which roles can access survey data and establishes the minimum response thresholds for each survey program. + +A **minimum response threshold** is the lowest number of responses a survey item must receive for its results to be reported. The higher the threshold, the less likely it is that users reviewing a survey report are able to infer the identity of an individual survey taker. + + - By default, the minimum response threshold for rating or multiple-choice items is five. + - For comments, the minimum response threshold is 10. + +Your organization can adjust the thresholds, higher or lower, for each survey program, and these thresholds are noted to survey takers. + +> [!IMPORTANT] +> Thresholds can't be lowered or raised for programs or cycles after it's launched. +> +> At the beginning of a survey, the privacy statement informs the participants whether the survey is confidential or identifiable and specifies its minimum response thresholds. Once a program is launched, response thresholds can't be changed. **Changing or altering a minimum response threshold requires a new survey program.** The previous program with the original confidentiality threshold can, however, be drawn into reports for comparison against new results with the new threshold. + +## Privacy is protected by managing reporting roles and permissions + +Your organization configures who views and configures survey reports at various levels. + +> **Example:** +> Your organization might use this reporting hierarchy for its marketing organization and assign permissions accordingly: +> - Marketing program managers (PMs) can only view survey results from the team they manage. +> - Marketing directors (to whom marketing PMs report) can view survey results for all teams reporting up to them. +> - The Chief Marketing Officer (to whom the marketing director reports) can view survey data for the entire marketing organization. + +Each reporting group feeds into a hierarchy level, or rollup, giving users visibility related to their role and authority. If the minimum response threshold isn't met for a user's team, their responses aren't reported. Instead, responses are aggregated with and rolled up to the next level. + +> **Example:** +> Consider a survey of the marketing organization in the example above - with the minimum reporting threshold set to five (5). A marketing PM can see aggregated survey responses for any item to which at least five team members responded. But if only four (4) responded to a specific item, the responses for that item aren't shown to the marketing PM. Instead, the responses are combined with those of other employees reporting up through the *marketing director* and rolled in to the next reporting level - the *marketing director*. + +## Comments threshold versus survey items threshold + +The default minimum response threshold for survey items is five (5), but for comments the default threshold is 10. + +Comments are easier to identify to a respondent. The report user might notice a writing style that is unique to a specific person. The smaller the group, the larger the potential to deduce the survey respondent. + +> **Example:** +> If a manager receives seven (7) responses from their team, they'll see an aggregated score but not the comments. On the other hand, if a manager receives 20 responses, they'll see the calculated score *and* the comments, regardless of the number of comments received. + +## Suppression thresholds add protection + +In some cases, even when the minimum response threshold is met, the ability to filter a report by attributes might allow a responder to be identified. In these cases, responses are **suppressed**,— they aren't reported even if the minimum response threshold is met. + +>[!IMPORTANT] +>The suppression threshold requires two (2) or more responses that separate the smallest attribute group from the next smallest group that meets the minimum response threshold. + +**Example - Marketing PM** +> - Five (5) of the six (6) team members are in North America; one (1) is in Europe. +> - The organization configured Glint to allow filtering of responses by survey taker region. +> - The survey's minimum response threshold is five (5). +> - All six (6) team members respond to an item that asks them to rate their manager's communication skills, from 'Very Good' to 'Very Poor.' +> - The North America team members all provide a rating of 'Very Good;' the European team member provide a rating of 'Very Poor.' + +>In this case, the marketing PM can't see the European score because, with only one (1) response from European employees, the minimum response threshold isn't met. But the PM can view the teamwide score (based on six responses) and North American-only score (based on five responses)—right? **No!** Those results are **suppressed**. + +>**Why?** + +> By comparing the teamwide score to the North American score, the PM might mathematically be able to determine the score received from the single European team member. When the PM sees that the North American score is 'Very Good,' but the teamwide score isn't, the user might infer that the European team member brought the average down. With a little math, the PM could calculate the exact score the European team member provided. +> +> For the North American score to be displayed, there must be more than two (2) responses within the overall team score that aren't within the North American group. So, if the overall team earned eight (8) responses where five (5) were from North America and three (3) were from Europe, the PM sees both the overall team score and the North American score. The, suppression threshold was met. + +>[!IMPORTANT] +>The suppression threshold requires two (2) or more responses that separate the smallest attribute group from the next smallest group that meets the minimum response threshold. + +**Example - Marketing PM** +> - Five (5) of the six (6) team members are in North America; one (1) is in Europe. +> - The organization configured Glint to allow filtering of responses by survey taker region. +> - The survey's minimum response threshold is five (5). +> - All six (6) team members respond to an item that asks them to rate their manager's communication skills, from 'Very Good' to 'Very Poor.' +> - The North America team members all provide a rating of 'Very Good;' the European team member provide a rating of 'Very Poor.' + +>In this case, the marketing PM can't see the European score because, with only one (1) response from European employees, the minimum response threshold isn't met. But the PM can view the teamwide score (based on six responses) and North American-only score (based on five responses)—right? **No!** Those results are **suppressed**. + +>**Why?** + +> By comparing the teamwide score to the North American score, the PM might mathematically be able to determine the score received from the single European team member. When the PM sees that the North American score is 'Very Good,' but the teamwide score isn't, the user might infer that the European team member brought the average down. With a little math, the PM could calculate the exact score the European team member provided. +> +> For the North American score to be displayed, there must be more than two (2) responses within the overall team score that aren't within the North American group. So, if the overall team earned eight (8) responses where five (5) were from North America and three (3) were from Europe, the PM sees both the overall team score and the North American score. The, suppression threshold was met. + +## More resources + +[Understand Glint confidentiality and suppression in reports](viva/glint/reports/confidentiality-suppression-reports) + + + + + + + From b6676d611dd2a172338bf0e6381728c813ca356d Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:32:37 -0400 Subject: [PATCH 13/20] Update viva-glint-survey-privacy.md --- Viva/glint/setup/viva-glint-survey-privacy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Viva/glint/setup/viva-glint-survey-privacy.md b/Viva/glint/setup/viva-glint-survey-privacy.md index be92d911d..20261dfca 100644 --- a/Viva/glint/setup/viva-glint-survey-privacy.md +++ b/Viva/glint/setup/viva-glint-survey-privacy.md @@ -1,6 +1,6 @@ --- title: How Viva Glint protects your privacy -description: Viva Glint is constantly evolving ways to protect confidentiality to encourage elevated levels of survey participation and honest and helpful feedback. +description: Viva Glint is constantly evolving ways to protect confidentiality to encourage high levels of survey participation and honest and helpful feedback. ms.author: JudithWeiner author: JudyWeiner manager: MelissaBarry From 3f2c6ebd678e9f5122b34d3075970f5a705b6528 Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:37:59 -0400 Subject: [PATCH 14/20] Update privacy-360-feedback.md --- Viva/glint/setup/privacy-360-feedback.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/Viva/glint/setup/privacy-360-feedback.md b/Viva/glint/setup/privacy-360-feedback.md index d61ac3f8b..d7509f00c 100644 --- a/Viva/glint/setup/privacy-360-feedback.md +++ b/Viva/glint/setup/privacy-360-feedback.md @@ -27,8 +27,6 @@ The confidentiality statement displayed for 360 feedback participants depends on > [!IMPORTANT] > Thresholds can't be lowered or raised for programs or cycles after it's launched. -https://learn.microsoft.com/en-us/viva/glint/setup/viva-glint-survey-privacy - |Feedback provider |Confidentiality threshold |Feedback provider response information setting |Confidentiality statement| |:----------|:-----------|:------------|:------------| |Self |1 |On or Off |Your feedback is visible to you and a limited number of people that are granted permission by your organization to view your 360 report. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | From 0039f1d5f1cc37f76c1a5492f89062d46f9537ca Mon Sep 17 00:00:00 2001 From: Judy Weiner <141166658+JudyWeiner@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:47:01 -0400 Subject: [PATCH 15/20] Update privacy-protection-reporting.md --- Viva/glint/setup/privacy-protection-reporting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Viva/glint/setup/privacy-protection-reporting.md b/Viva/glint/setup/privacy-protection-reporting.md index 0a495ffdd..3642bd69e 100644 --- a/Viva/glint/setup/privacy-protection-reporting.md +++ b/Viva/glint/setup/privacy-protection-reporting.md @@ -100,7 +100,7 @@ In some cases, even when the minimum response threshold is met, the ability to f ## More resources -[Understand Glint confidentiality and suppression in reports](viva/glint/reports/confidentiality-suppression-reports) +[Understand Glint reporting and confidentiality](/viva/glint/reports/confidentiality-suppression-reports) From a984b5a15f6fe467ac4c52f61db9c99e213d2d14 Mon Sep 17 00:00:00 2001 From: Alicia Weixelman Date: Mon, 7 Oct 2024 14:22:32 -0500 Subject: [PATCH 16/20] Update sftp-data-automation.md --- Viva/glint/setup/sftp-data-automation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Viva/glint/setup/sftp-data-automation.md b/Viva/glint/setup/sftp-data-automation.md index 76e36c4cc..57b4473f6 100644 --- a/Viva/glint/setup/sftp-data-automation.md +++ b/Viva/glint/setup/sftp-data-automation.md @@ -14,7 +14,7 @@ search-appverid: MET150 ms.topic: article ms.service: viva-glint ms.localizationpriority: high -ms.date: 08/13/2024 +ms.date: 10/07/2024 --- # Understand Viva Glint SFTP and data automation @@ -57,7 +57,7 @@ In your SFTP account, there are two (2) directories that Viva Glint monitors for > - Files that cause warnings and errors can be downloaded from the **Activity Audit Log** in **General Settings** for 28 days after import. > [!TIP] -> For SAP Success Factors and Workday, "/files" may be auto-appended to the file path for SFTP transmissions. Remove "/files" from the file path ("/user_full" or "/user_delta") to prevent upload errors if your HRIS auto-appended "/files". +> For some versions of SAP Success Factors and Workday, "/files" may be auto-appended to the file path for SFTP transmissions. Remove "/files" from the file path ("/user_full" or "/user_delta") to prevent upload errors if your HRIS version auto-appends "/files". ## Transfer methods From 062375251b7fe48f130664709f016d4a0cf7f8fb Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:07:22 -0700 Subject: [PATCH 17/20] Acrolinx: minimal changes to get to 80 --- Viva/glint/setup/privacy-360-feedback.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Viva/glint/setup/privacy-360-feedback.md b/Viva/glint/setup/privacy-360-feedback.md index d7509f00c..000c518dc 100644 --- a/Viva/glint/setup/privacy-360-feedback.md +++ b/Viva/glint/setup/privacy-360-feedback.md @@ -30,9 +30,9 @@ The confidentiality statement displayed for 360 feedback participants depends on |Feedback provider |Confidentiality threshold |Feedback provider response information setting |Confidentiality statement| |:----------|:-----------|:------------|:------------| |Self |1 |On or Off |Your feedback is visible to you and a limited number of people that are granted permission by your organization to view your 360 report. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | -|**Non-subject**: Manager, Skip-level manager, or Custom |1 |On or Off |Note that this is an identifiable survey, which means Contoso will be able to see that your survey responses came from you. Whether you responded, as well as your feedback, will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | -|**Non-subject**: Directs, Peers, Colleagues, or Custom |3 or more |Off |Your responses are confidential and reported to Contoso in aggregate groups of 3 or more respondents, including any write-in comments which are reported verbatim. Take care not to identify yourself in the comments. Your aggregated feedback will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md), which describes other ways your data may be accessed, and your organization's Privacy Policy for more information. | -|**Non-subject**: Directs, Peers, Colleagues, or Custom |3 or more |On |Your responses are confidential and reported to Contoso in aggregate groups of 3 or more respondents, including any write-in comments which are reported verbatim. Take care not to identify yourself in the comments. Whether you responded, as well as your aggregated feedback, will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md), which describes other ways your data may be accessed, and your organization's Privacy Policy for more information. | +|**Non-subject**: Manager, Skip-level manager, or Custom |1 |On or Off |This is an identifiable survey, which means Contoso will be able to see that your survey responses came from you. Whether you responded, as well as your feedback, will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See your organization’s Privacy Policy for more information. Learn how Viva Glint handles survey responses in [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md). | +|**Non-subject**: Directs, Peers, Colleagues, or Custom |3 or more |Off |Your responses are confidential and reported to Contoso in aggregate groups of three or more respondents, including any write-in comments which are reported verbatim. Take care not to identify yourself in the comments. Your aggregated feedback will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md), which describes other ways your data may be accessed, and your organization's Privacy Policy for more information. | +|**Non-subject**: Directs, Peers, Colleagues, or Custom |3 or more |On |Your responses are confidential and reported to Contoso in aggregate groups of three or more respondents, including any write-in comments which are reported verbatim. Take care not to identify yourself in the comments. Whether you responded, as well as your aggregated feedback, will be visible to _`<360 subject’s full name>`_ and people that are granted permission by your organization. See [Microsoft Viva Glint Reporting and Confidentiality Rules](viva-glint-survey-privacy.md), which describes other ways your data may be accessed, and your organization's Privacy Policy for more information. | > [!IMPORTANT] > - "Contoso" and confidentiality thresholds in statements pull in your organization's name and threshold information. From 05fdd2b89163c9c49b7a764903c06596f97af7c4 Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:09:58 -0700 Subject: [PATCH 18/20] Remove unnecessary angle brackets --- .../setup/privacy-protection-reporting.md | 70 +++++++++---------- 1 file changed, 35 insertions(+), 35 deletions(-) diff --git a/Viva/glint/setup/privacy-protection-reporting.md b/Viva/glint/setup/privacy-protection-reporting.md index 3642bd69e..dcdb54d2a 100644 --- a/Viva/glint/setup/privacy-protection-reporting.md +++ b/Viva/glint/setup/privacy-protection-reporting.md @@ -24,8 +24,8 @@ Survey takers' privacy is protected by setting and communicating a minimum numbe A **minimum response threshold** is the lowest number of responses a survey item must receive for its results to be reported. The higher the threshold, the less likely it is that users reviewing a survey report are able to infer the identity of an individual survey taker. - - By default, the minimum response threshold for rating or multiple-choice items is five. - - For comments, the minimum response threshold is 10. +- By default, the minimum response threshold for rating or multiple-choice items is five. +- For comments, the minimum response threshold is 10. Your organization can adjust the thresholds, higher or lower, for each survey program, and these thresholds are noted to survey takers. @@ -38,16 +38,16 @@ Your organization can adjust the thresholds, higher or lower, for each survey pr Your organization configures who views and configures survey reports at various levels. -> **Example:** -> Your organization might use this reporting hierarchy for its marketing organization and assign permissions accordingly: -> - Marketing program managers (PMs) can only view survey results from the team they manage. -> - Marketing directors (to whom marketing PMs report) can view survey results for all teams reporting up to them. -> - The Chief Marketing Officer (to whom the marketing director reports) can view survey data for the entire marketing organization. +**Example:** +Your organization might use this reporting hierarchy for its marketing organization and assign permissions accordingly: +- Marketing program managers (PMs) can only view survey results from the team they manage. +- Marketing directors (to whom marketing PMs report) can view survey results for all teams reporting up to them. +- The Chief Marketing Officer (to whom the marketing director reports) can view survey data for the entire marketing organization. Each reporting group feeds into a hierarchy level, or rollup, giving users visibility related to their role and authority. If the minimum response threshold isn't met for a user's team, their responses aren't reported. Instead, responses are aggregated with and rolled up to the next level. -> **Example:** -> Consider a survey of the marketing organization in the example above - with the minimum reporting threshold set to five (5). A marketing PM can see aggregated survey responses for any item to which at least five team members responded. But if only four (4) responded to a specific item, the responses for that item aren't shown to the marketing PM. Instead, the responses are combined with those of other employees reporting up through the *marketing director* and rolled in to the next reporting level - the *marketing director*. +**Example:** +Consider a survey of the marketing organization in the example above - with the minimum reporting threshold set to five (5). A marketing PM can see aggregated survey responses for any item to which at least five team members responded. But if only four (4) responded to a specific item, the responses for that item aren't shown to the marketing PM. Instead, the responses are combined with those of other employees reporting up through the *marketing director* and rolled in to the next reporting level - the *marketing director*. ## Comments threshold versus survey items threshold @@ -55,48 +55,48 @@ The default minimum response threshold for survey items is five (5), but for com Comments are easier to identify to a respondent. The report user might notice a writing style that is unique to a specific person. The smaller the group, the larger the potential to deduce the survey respondent. -> **Example:** -> If a manager receives seven (7) responses from their team, they'll see an aggregated score but not the comments. On the other hand, if a manager receives 20 responses, they'll see the calculated score *and* the comments, regardless of the number of comments received. +**Example:** +If a manager receives seven (7) responses from their team, they'll see an aggregated score but not the comments. On the other hand, if a manager receives 20 responses, they'll see the calculated score *and* the comments, regardless of the number of comments received. ## Suppression thresholds add protection In some cases, even when the minimum response threshold is met, the ability to filter a report by attributes might allow a responder to be identified. In these cases, responses are **suppressed**,— they aren't reported even if the minimum response threshold is met. ->[!IMPORTANT] ->The suppression threshold requires two (2) or more responses that separate the smallest attribute group from the next smallest group that meets the minimum response threshold. +> [!IMPORTANT] +> The suppression threshold requires two (2) or more responses that separate the smallest attribute group from the next smallest group that meets the minimum response threshold. **Example - Marketing PM** -> - Five (5) of the six (6) team members are in North America; one (1) is in Europe. -> - The organization configured Glint to allow filtering of responses by survey taker region. -> - The survey's minimum response threshold is five (5). -> - All six (6) team members respond to an item that asks them to rate their manager's communication skills, from 'Very Good' to 'Very Poor.' -> - The North America team members all provide a rating of 'Very Good;' the European team member provide a rating of 'Very Poor.' +- Five (5) of the six (6) team members are in North America; one (1) is in Europe. +- The organization configured Glint to allow filtering of responses by survey taker region. +- The survey's minimum response threshold is five (5). +- All six (6) team members respond to an item that asks them to rate their manager's communication skills, from 'Very Good' to 'Very Poor.' +- The North America team members all provide a rating of 'Very Good;' the European team member provide a rating of 'Very Poor.' ->In this case, the marketing PM can't see the European score because, with only one (1) response from European employees, the minimum response threshold isn't met. But the PM can view the teamwide score (based on six responses) and North American-only score (based on five responses)—right? **No!** Those results are **suppressed**. +In this case, the marketing PM can't see the European score because, with only one (1) response from European employees, the minimum response threshold isn't met. But the PM can view the teamwide score (based on six responses) and North American-only score (based on five responses)—right? **No!** Those results are **suppressed**. ->**Why?** +**Why?** -> By comparing the teamwide score to the North American score, the PM might mathematically be able to determine the score received from the single European team member. When the PM sees that the North American score is 'Very Good,' but the teamwide score isn't, the user might infer that the European team member brought the average down. With a little math, the PM could calculate the exact score the European team member provided. -> -> For the North American score to be displayed, there must be more than two (2) responses within the overall team score that aren't within the North American group. So, if the overall team earned eight (8) responses where five (5) were from North America and three (3) were from Europe, the PM sees both the overall team score and the North American score. The, suppression threshold was met. +By comparing the teamwide score to the North American score, the PM might mathematically be able to determine the score received from the single European team member. When the PM sees that the North American score is 'Very Good,' but the teamwide score isn't, the user might infer that the European team member brought the average down. With a little math, the PM could calculate the exact score the European team member provided. + +For the North American score to be displayed, there must be more than two (2) responses within the overall team score that aren't within the North American group. So, if the overall team earned eight (8) responses where five (5) were from North America and three (3) were from Europe, the PM sees both the overall team score and the North American score. The, suppression threshold was met. ->[!IMPORTANT] ->The suppression threshold requires two (2) or more responses that separate the smallest attribute group from the next smallest group that meets the minimum response threshold. +> [!IMPORTANT] +> The suppression threshold requires two (2) or more responses that separate the smallest attribute group from the next smallest group that meets the minimum response threshold. **Example - Marketing PM** -> - Five (5) of the six (6) team members are in North America; one (1) is in Europe. -> - The organization configured Glint to allow filtering of responses by survey taker region. -> - The survey's minimum response threshold is five (5). -> - All six (6) team members respond to an item that asks them to rate their manager's communication skills, from 'Very Good' to 'Very Poor.' -> - The North America team members all provide a rating of 'Very Good;' the European team member provide a rating of 'Very Poor.' +- Five (5) of the six (6) team members are in North America; one (1) is in Europe. +- The organization configured Glint to allow filtering of responses by survey taker region. +- The survey's minimum response threshold is five (5). +- All six (6) team members respond to an item that asks them to rate their manager's communication skills, from 'Very Good' to 'Very Poor.' +- The North America team members all provide a rating of 'Very Good;' the European team member provide a rating of 'Very Poor.' ->In this case, the marketing PM can't see the European score because, with only one (1) response from European employees, the minimum response threshold isn't met. But the PM can view the teamwide score (based on six responses) and North American-only score (based on five responses)—right? **No!** Those results are **suppressed**. +In this case, the marketing PM can't see the European score because, with only one (1) response from European employees, the minimum response threshold isn't met. But the PM can view the teamwide score (based on six responses) and North American-only score (based on five responses)—right? **No!** Those results are **suppressed**. ->**Why?** +**Why?** -> By comparing the teamwide score to the North American score, the PM might mathematically be able to determine the score received from the single European team member. When the PM sees that the North American score is 'Very Good,' but the teamwide score isn't, the user might infer that the European team member brought the average down. With a little math, the PM could calculate the exact score the European team member provided. -> -> For the North American score to be displayed, there must be more than two (2) responses within the overall team score that aren't within the North American group. So, if the overall team earned eight (8) responses where five (5) were from North America and three (3) were from Europe, the PM sees both the overall team score and the North American score. The, suppression threshold was met. +By comparing the teamwide score to the North American score, the PM might mathematically be able to determine the score received from the single European team member. When the PM sees that the North American score is 'Very Good,' but the teamwide score isn't, the user might infer that the European team member brought the average down. With a little math, the PM could calculate the exact score the European team member provided. + +For the North American score to be displayed, there must be more than two (2) responses within the overall team score that aren't within the North American group. So, if the overall team earned eight (8) responses where five (5) were from North America and three (3) were from Europe, the PM sees both the overall team score and the North American score. The, suppression threshold was met. ## More resources From 117a721a182bb760fae7751c3dba0e2675bc25e3 Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:17:29 -0700 Subject: [PATCH 19/20] Remove redundant "Here's an example of a results file:" --- Viva/insights/advanced/analyst/query-results.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/Viva/insights/advanced/analyst/query-results.md b/Viva/insights/advanced/analyst/query-results.md index bff73a78f..e82044789 100644 --- a/Viva/insights/advanced/analyst/query-results.md +++ b/Viva/insights/advanced/analyst/query-results.md @@ -171,8 +171,6 @@ When you define a query, you select metrics and employee attributes. After the q 2. Select to open and right-click the zip file, which contains a .csv version of the data, and then select **Extract All** and extract the .csv to a local folder. 3. Open the extracted .csv file using Excel. - Here's an example of a results file: - Here's an example of a results file: :::image type="content" source="../images/query-csv-output.png" alt-text="Screenshot that an example .csv results file."::: From 1f216ffbb2e69978a56ec7b78166697f2c5acada Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Mon, 7 Oct 2024 14:18:45 -0700 Subject: [PATCH 20/20] Add lightbox to aid legibility --- Viva/insights/advanced/analyst/query-results.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Viva/insights/advanced/analyst/query-results.md b/Viva/insights/advanced/analyst/query-results.md index e82044789..845fa16d2 100644 --- a/Viva/insights/advanced/analyst/query-results.md +++ b/Viva/insights/advanced/analyst/query-results.md @@ -87,7 +87,7 @@ To access content filters, select the **+** icon to the right of the **Custom qu Then, use the dropdown menus to select your filter. -:::image type="content" source="../images/query-results-select-content-filter.png" alt-text="Screenshot that shows the new content filter button selected and the Power BI templates option expanded below."::: +:::image type="content" source="../images/query-results-select-content-filter.png" alt-text="Screenshot that shows the new content filter button selected and the Power BI templates option expanded below." lightbox="../images/query-results-select-content-filter.png"::: While you can only use one content filter active at a time, you can have up to five filters available. Filters won’t carry over from one session to the next.