Merge pull request #8673 from MicrosoftDocs/main

Publish main to live 10/07/2024, 3:30 PM

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

Viva/glint/setup/privacy-360-feedback.md

@@ -0,0 +1,40 @@
+---
+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
+audience: admin
+ms.collection: 
+- essentials-privacy
+f1.keywords: NOCSH
+keywords: Thresholds, suppression, response rate, suppressed data, 
+ - m365initiative-viva
+ - selfserve
+search-appverid: MET150
+ms.topic: concept-article
+ms.service: viva-glint
+ms.localizationpriority: high
+ms.date: 10/07/2024
+---
+
+# 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. 
+
+|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 |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.
+> - 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).
+

Viva/glint/setup/privacy-protection-reporting.md

@@ -0,0 +1,110 @@
+---
+title: Privacy protection within feedback reporting
+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
+audience: admin
+ms.collection: 
+- essentials-privacy
+f1.keywords: NOCSH
+keywords: Thresholds, suppression, response rate, suppressed data, comments threshold, survey items threshold
+ - 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
+
+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 reporting and confidentiality](/viva/glint/reports/confidentiality-suppression-reports)
+
+
+
+
+
+
+

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