Merge pull request #8768 from MicrosoftDocs/main

Publish main to live, Monday 10:30 AM PST, 10/28

Viva/glint/setup/advanced-config-uploads.md

@@ -13,7 +13,7 @@ search-appverid: MET150
 ms.topic: article
 ms.service: viva-glint
 ms.localizationpriority: high
-ms.date: 10/17/2024
+ms.date: 10/28/2024
 ---
 
 # Use Advanced Configuration Uploads
@@ -51,18 +51,18 @@ When several users need customized data access to their Viva Glint Dashboards, u
 1. In the **Load import file into database?** dialog, select **Yes**.
 1. Go to some users' profiles to confirm that customized access appears as expected.
 
-For example, the custom data access for this user:
+   For example, the custom data access for this user:
 
-|manager reference  |population   |add or remove|survey uuid |Cost Center |Manager Level 1 |Region |Country |City |
-|----------|-----------|------------|------------|------------|------------|------------|------------|------------|
-|[email protected]|0 |ADD|aa1aa1aa-a1a1-1a1a-1a1a-111111111a11|37651 | | | | |
-|[email protected]|0 |ADD|aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 |17123 | | | | |
-|[email protected]|1 |ADD|aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 | |7890 | | | |
-|[email protected]|2 |ADD|aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 | | |EMEA |Ireland |Dublin |
+   |manager reference  |population   |add or remove|survey uuid |Cost Center |Manager Level 1 |Region |Country |City |
+   |----------|-----------|------------|------------|------------|------------|------------|------------|------------|
+   |[email protected]|0 |ADD|aa1aa1aa-a1a1-1a1a-1a1a-111111111a11|37651 | | | | |
+   |[email protected]|0 |ADD|aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 |17123 | | | | |
+   |[email protected]|1 |ADD|aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 | |7890 | | | |
+   |[email protected]|2 |ADD|aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 | | |EMEA |Ireland |Dublin |
 
-Displays on Ana's profile like this:
+   Displays on Ana's profile like this:
 
-:::image type="content" source="../../media/glint/setup/glint-custom-access.png" alt-text="Screenshot of a user's custom Cost Center, Manager Team, and Location access.":::
+   :::image type="content" source="../../media/glint/setup/glint-custom-access.png" alt-text="Screenshot of a user's custom Cost Center, Manager Team, and Location access.":::
 
 ## Perform Retroactive User Updates
 
@@ -80,9 +80,14 @@ When a survey closes, employee attributes that display in reporting aren't updat
 ### To perform a Retroactive User Updates upload:
 
 > [!CAUTION]
-> Do not perform a retroactive update while a Viva Glint survey is live.
+> - Do not perform a retroactive update while a Viva Glint survey is live.
+> - Deleted user data can't be retroactively updated.
 
 1. Export survey cycle data with the EXPORT_USERS_FROM_SURVEY_CYCLE Data App for the surveys that need to be updated. [Learn more](glint-data-apps.md).
+
+   > [!NOTE]
+   > Keep this export of original survey cycle data in case any retroactive updates need to be reverted.
+
 1. Prepare an update file with the EXPORT_USERS_FROM_SURVEY_CYCLE file from Step 1.
    1. To preserve special characters and formatting, always open files by [importing data from .csv](https://go.microsoft.com/fwlink/?linkid=2247414) in Microsoft Excel.
    1. Delete all columns except for First Name, Last Name, Email, Employee ID, Status, and the attributes that need to be retroactively updated (for example, Department).

Viva/glint/setup/custom-access.md

@@ -43,7 +43,7 @@ The custom data access export includes the following information. Modify or add
 |Column  |Description   |
 |:----------|:-----------|
 |user email     | Populated with users' email addresses.       |
-|population     | Enter 1 for the first population. Each new population increases in number for each user. |
+|population     | The first population shows as 1. Each new population increases in number for each user. |
 |access type   | <ul><li>The survey uuid of the program that users have customized access for, or</li> <li>"GOAL" when exporting Focus Area access for users.</li> </ul>      |
 |other attributes    | Other columns in the export are based on your organization's attributes and values that are used to grant custom access. To grant new access, add new columns and values. |
 
@@ -65,31 +65,39 @@ To prepare your exported custom access file for import to Advanced Configuration
    > [!NOTE]
    > To prevent upload errors, for attributes based on data uploaded to Glint make sure that column labels match your attribute setup exactly.
  
-3. To grant custom access for:
+3. Edit values in the population column. The first population that a user has access to should be changed from a 1 to a 0, with each new population increasing in number.
+
+   |Population value |Becomes...   |
+   |:----------|:-----------|
+   |1    | 0 |
+   |2    | 1 |
+   |3    | 2 |
+
+5. To grant custom access for:
    - **Survey results**:
       - Populate the survey uuid column with the survey programs unique ID that's included in the access export file.
    - **Focus Areas**:
       - Populate the survey uuid column with "GOAL."
    - **Admin permissions**:
       - Populate the survey uuid column with "ADMIN."
-4. To grant custom access to: 
+6. To grant custom access to: 
    - **Another manager's team that exists in current employee data**:
       - Include an attribute column labeled: Manager Level 1 and list the Employee ID of the manager that another user should have access to. The manager levels automatically calculate based on the manager ID added to the Manager Level 1 column.
    - **Another manager's team that doesn't exist in current employee data**:
       - Include columns for all Manager Level fields populated with manager IDs to build the full manager hierarchy path. To get all levels in this past hierarchy path for an old manager team, [export users from the survey cycle](/viva/glint/setup/glint-data-apps#export_users_from_survey_cycle) and copy Manager Level fields and the manager IDs in them.
    - **A level in a non-Manager hierarchy**:
       - Include all levels above the level the user should have access to. Example: To grant access to Location Hierarchy Level 3 = Dublin, include columns for Region, Country, and City.
-5. Save your file in .csv format with a comma separator and UTF-8 encoding.
+7. Save your file in .csv format with a comma separator and UTF-8 encoding.
 
 ### Example
 
 An HR business partner, [email protected], oversees European Sales and Marketing teams for Contoso. To grant this user access to the right cut of data to view survey results, a Viva Glint Admin would fill in an access file with their location attribute Region = Europe and their hierarchy Team Level 1 = Marketing and Sales.
 
-:::image type="content" source="../../media/glint/setup/custom-access-export-survey2.png" alt-text="Screenshot of a custom access export for a user with customized survey results access.":::
+:::image type="content" source="../../media/glint/setup/custom-access-export-survey3.png" alt-text="Screenshot of a custom access export for a user with customized survey results access.":::
 
 To apply the same custom access for creating Focus Areas, update the access type column for this user to "GOAL."
 
-:::image type="content" source="../../media/glint/setup/custom-access-export-focus-area2.png" alt-text="Screenshot of a custom access export for a user with customized focus area access.":::
+:::image type="content" source="../../media/glint/setup/custom-access-export-focus-area3.png" alt-text="Screenshot of a custom access export for a user with customized focus area access.":::
 
 > [!IMPORTANT]
 > Save your edited file as **.csv with a comma separator and UTF-8 encoding**.

Viva/glint/setup/glint-data-apps.md

@@ -48,17 +48,22 @@ For one or multiple survey cycles, export a snapshot of employee data as they we
 
 When a survey closes, Manager Hierarchy information that displays in reporting isn't updated with usual employee data uploads. To update data in reporting, use the Retroactive Pulse Update Data App to apply new values.
 
-If your update doesn't involve Manager Hierarchy, use the [Retroactive Upload](https://go.microsoft.com/fwlink/?linkid=2247341) feature instead.
+If your update doesn't involve Manager Hierarchy, use the [Retroactive Upload](advanced-config-uploads.md) feature instead.
 
 > [!CAUTION]
-> Do not perform a retroactive update while a Viva Glint survey is live.
+> - Do not perform a retroactive update while a Viva Glint survey is live.
+> - Deleted user data can't be retroactively updated.
 
 ### To perform a retroactive update to Manager Hierarchy:
 
 Use these steps when manager reporting lines need to be corrected for a closed survey.
 
 1. Export current employee data from the Glint People page to preserve employees and Manager IDs in their current state. When the retroactive update is complete, you'll reload this data to reset users to their current information.
 1. Export survey cycle data with the EXPORT_USERS_FROM_SURVEY_CYCLE Data App for the survey needs to be updated.
+
+   > [!NOTE]
+   > Keep this export of original survey cycle data in case any retroactive updates need to be reverted.
+      
 1. Prepare an update file with the EXPORT_USERS_FROM_SURVEY_CYCLE file from Step 2.
 
    > [!IMPORTANT]
@@ -109,7 +114,7 @@ Use these steps when manager reporting lines need to be corrected for a closed s
 1. Confirm Manager Hierarchy changes in your **Dashboard** and **Reports**.
 1. If the user data updates made by the correction file loaded for this update should be reset to current attribute values, load the data exported in Step 1 to the Glint People page.
    1. For example, if Manager corrections apply to survey data in the past, but Manager IDs now different for employees, load data exported in Step 1 to restore current information.
-3. Optionally, [delete the Distribution List](https://go.microsoft.com/fwlink/?linkid=2281078) created to target users for the update.
+3. Optionally, [delete the Distribution List](set-up-distribution-lists.md#delete-distribution-lists) created to target users for the update.
 
 > [!NOTE]
 > Depending on the number of Manager ID updates and users involved, it may take up to an hour to see changes reflected in reporting.

Viva/glint/setup/insights-integration.md

@@ -14,7 +14,7 @@ search.appverid: MET150
 ms.topic: article
 ms.service: viva-glint
 ms.localizationpriority: high
-ms.date: 09/09/2024
+ms.date: 10/28/2024
 ---
 
 # Send Viva Glint survey results to Viva Insights (public preview)
@@ -34,11 +34,6 @@ This article discusses how to import survey results – employee-level survey re
 1. The Viva Insights admin contacts the Viva Glint admin to share Viva Glint survey data, and the Viva Glint admin selects specific survey programs and sends the data to Viva Insights.
 1. Viva Insights validates and processes the data so it’s ready for use. 
 
->[!IMPORTANT]
->Please be advised of a current limitation in the Glint admin UI: **All** Viva Insights purchased license counts are showing instead of only the applied/deployed license counts. Expect this bug to be fixed by the end of September 2024.  
-
-Counts are in this UI on the Glint admin integration config landing page
-
 ## What data can be sent to Viva Insights?
 
 >[!IMPORTANT]

Viva/glint/setup/insights-to-glint.md

@@ -14,7 +14,7 @@ search.appverid: MET150
 ms.topic: article
 ms.service: viva-glint
 ms.localizationpriority: high
-ms.date: 10/08/2024
+ms.date: 10/28/2024
 ---
 
 # Send Viva Insights data into Viva Glint (public preview)
@@ -25,9 +25,7 @@ The following procedure requires these roles:
 
 >[!IMPORTANT]
 >This feature is currently available to public preview customers only. Features described here are subject to change.
->
->Also, please be advised of a current limitation in the Glint admin UI: *All* Viva Insights purchased license counts are showing instead of only the applied/deployed license counts.
->
+
 Glint customers can import behavioral data from Microsoft Viva Insights to supplement their Viva Glint survey data for a better understanding of how your organization’s way of working impacts the employee experience.
 
 -	Explore employee sentiment relative to behaviors
@@ -183,7 +181,7 @@ All data ranges are the same across the entire company.
 1.	Adjust the range in the **Max** column.
 2.	Select **Save**.
 
-:::image type="content" source="../../media/glint/setup/glintsights-customize-ranges.png" alt-text="Screenshot of the Customize Ranges window.":::
+    :::image type="content" source="../../media/glint/setup/glintsights-customize-ranges.png" alt-text="Screenshot of the Customize Ranges window.":::
 
 > [!IMPORTANT]
 > Glint respects Viva Insights confidentiality thresholds, in addition to Glint’s threshold. Customizing default ranges may result in ranges with employees less than these thresholds and for this reason, results don’t appear in any reports or filters.

Viva/glint/setup/set-up-sftp.md

@@ -14,7 +14,7 @@ search-appverid: MET150
 ms.topic: article
 ms.service: viva-glint
 ms.localizationpriority: high
-ms.date: 09/23/2024
+ms.date: 10/28/2024
 ---
 
 # Set up Secure File Transfer Protocol (SFTP) in Viva Glint
@@ -25,7 +25,7 @@ Use Microsoft Viva Glint [Secure File Transfer Protocol (SFTP)](sftp-data-automa
 - Specify public IP addresses to connect (optional)
 - Select users that receive data upload notification emails
 - Set up PGP encryption (optional)
-- View credentials to access your SFTP account
+- View credentials and select a port number to access your SFTP account
 
 Your IT team may need to add an IP exception or add hosts and ports to an allowlist to connect to SFTP. [Learn more](allowed-list.md). 
 
@@ -46,7 +46,7 @@ Manage SFTP settings to connect to your Viva Glint SFTP account:
 |**SFTP IP Addresses**     |Optional       |<ul><li>**Leave this field blank to allow any account to connect.**</li><li>Specify public IP addresses to limit accounts that can connect.</li><li>Contact your IT team, HR information system (HRIS) vendor, or use [online tools](https://ifconfig.io/) to determine your public IP addresses.</li><li>This field supports subnets, or ranges of IP addresses. Enter ranges (for example: 1.1.1.0/24) rather than individual IP addresses in each field, if needed.</li></ul>     |
 |**Notify People**     |Required       |<ul><li>Search for and add users that should receive file upload notification emails.</li><li>Users must be active and exist in Viva Glint.</li></ul>       |
 |**PGP Encryption**     |Optional       |<ul><li>Switch toggle to **On** to enable file encryption and reveal Glint's public PGP key to encrypt employee data files.</li><li>When this setting is enabled, SFTP accepts files with and without encryption.</li></ul>      |
-|**SFTP Credentials**     |Required       |<ul><li>Use the credentials shown in the platform to connect to SFTP. Allow at least one hour after entering public SSH keys and optional IP addresses before testing your connection.</li><br><br><li>**File Protocol**: _SFTP_</li><li>**Port**: Select 22 or 1122</li> <li>**Host Name**: _Varies based on region (US or EU) and selected port_</li> <li>**Username:** _Company ID_</li> <li>**Password:** _Not applicable, use your private SSH key file_</li></ul>        |
+|**SFTP Credentials**     |Required       |After selecting a port number (22 or 1122), copy credentials shown in the platform to connect to SFTP. Your host name changes based on your region (US or EU) and selected port. Allow at least one hour after entering public SSH keys and optional IP addresses before testing your connection.<br><br><ul><li>**File Protocol**: _SFTP_</li><li>**Port**: Select 22 or 1122</li> <li>**Host Name**: _Varies based on region (US or EU) and selected port. Copy from the platform for the correct host name._</li> <li>**Username:** _Company ID_</li> <li>**Password:** _Not applicable, use your private SSH key file_</li></ul>        |
 
 > [!IMPORTANT]
 > Private IP ranges aren't internet routable and don't allow SFTP connection. Don't include private IP addresses, which fall in these ranges:

Viva/glint/setup/update-glint-reporting-data.md

@@ -13,15 +13,16 @@ search-appverid: MET150
 ms.topic: article
 ms.service: viva-glint
 ms.localizationpriority: high
-ms.date: 09/05/2024
+ms.date: 10/28/2024
 ---
 
 # How to update reporting data in closed Viva Glint surveys
 
 For highly trained users, Microsoft Viva Glint Advanced Configuration Uploads and Data Apps allow you to perform retroactive updates to survey data. Use this guidance to determine which retroactive update option best meets your needs.
 
 > [!CAUTION]
-> Do not perform a retroactive update while a Glint survey is live.
+> - Don't perform a retroactive update while a Glint survey is live.
+> - Deleted user data can't be retroactively updated.
 
 ## Attributes that don't require retroactive updates