Organization Data Upload

Sanjanaa_Ellur
Community Manager
Community Manager

What data is required to be uploaded to set up WpA? What should the frequency of these uploads be in order to keep the analyzed data updated? In the upload, what will the aggregation process be like and what criteria will be used?

2 ACCEPTED SOLUTIONS

Sanjanaa_Ellur
Community Manager
Community Manager

What data is required to be uploaded to set up WpA? What should the frequency of these uploads be in order to keep the analyzed data updated?

Supporting documentation:

https://docs.microsoft.com/en-us/viva/insights/setup/prepare-organizational-data 
https://docs.microsoft.com/en-us/viva/insights/setup/upload-organizational-data-1st 
https://docs.microsoft.com/en-us/viva/insights/setup/upload-organizational-data

An initial Org Data upload is required to inform the system and provide background information to the O365 collaboration signals (all based on email addresses).

The required fields are:

• Employee and Manager Email address (SMTP) – important for the system to understand the org hierarchy and
interactions between Employees and Managers
• Department (Organization) that allows you to analyse interactions and collaboration between Departments
• Level Designation (Grade) to determine differences across Managerial levels to see how they collaborate differently

For a pilot, only 1 upload will be necessary but for ongoing use of the system, we recommend a monthly update of fresh information to introduce new joiners and identify changes in structure
etc. Additional measures/attributes can also be added to the file (such as Location, Hire date, Tenure/Years of service, Performance measures, Engagement information etc.)

View solution in original post

Sanjanaa_Ellur
Community Manager
Community Manager

In the upload, what will the aggregation process be like and what criteria will be used?

Supporting documentation:

https://docs.microsoft.com/en-us/viva/insights/privacy/de-identify-data 
https://docs.microsoft.com/en-us/viva/insights/privacy/privacy-and-data-access

For confidentiality reasons, the Employee and Manager Email addresses that are associated with O365 signals (in Teams – Calls and IMs, in Outlook – Meetings and Emails) are always hashed to protect individuals during the initial upload process. Any reports, outputs or information generated by the system cannot be traced back to its point of origin unless a Company uploads any Unique identifiers (such as Social Security numbers, Payroll Numbers, Names etc.). This is strongly discouraged.

The system has strict access control where Roles are assigned to access and use the system:

• An Analyst can have full or limited access allowing them to view the information, run queries and generate reports or data extracts
• An Administrator can control Settings and upload new Org Data files

Any groups with less than 5 people is also automatically hidden to ensure privacy:

In this example, the company has less than 5 Senior Execs so their information is hidden by the system.

Sanjanaa_Ellur_0-1635272914511.png

 

View solution in original post

2 REPLIES 2

Sanjanaa_Ellur
Community Manager
Community Manager

What data is required to be uploaded to set up WpA? What should the frequency of these uploads be in order to keep the analyzed data updated?

Supporting documentation:

https://docs.microsoft.com/en-us/viva/insights/setup/prepare-organizational-data 
https://docs.microsoft.com/en-us/viva/insights/setup/upload-organizational-data-1st 
https://docs.microsoft.com/en-us/viva/insights/setup/upload-organizational-data

An initial Org Data upload is required to inform the system and provide background information to the O365 collaboration signals (all based on email addresses).

The required fields are:

• Employee and Manager Email address (SMTP) – important for the system to understand the org hierarchy and
interactions between Employees and Managers
• Department (Organization) that allows you to analyse interactions and collaboration between Departments
• Level Designation (Grade) to determine differences across Managerial levels to see how they collaborate differently

For a pilot, only 1 upload will be necessary but for ongoing use of the system, we recommend a monthly update of fresh information to introduce new joiners and identify changes in structure
etc. Additional measures/attributes can also be added to the file (such as Location, Hire date, Tenure/Years of service, Performance measures, Engagement information etc.)

Sanjanaa_Ellur
Community Manager
Community Manager

In the upload, what will the aggregation process be like and what criteria will be used?

Supporting documentation:

https://docs.microsoft.com/en-us/viva/insights/privacy/de-identify-data 
https://docs.microsoft.com/en-us/viva/insights/privacy/privacy-and-data-access

For confidentiality reasons, the Employee and Manager Email addresses that are associated with O365 signals (in Teams – Calls and IMs, in Outlook – Meetings and Emails) are always hashed to protect individuals during the initial upload process. Any reports, outputs or information generated by the system cannot be traced back to its point of origin unless a Company uploads any Unique identifiers (such as Social Security numbers, Payroll Numbers, Names etc.). This is strongly discouraged.

The system has strict access control where Roles are assigned to access and use the system:

• An Analyst can have full or limited access allowing them to view the information, run queries and generate reports or data extracts
• An Administrator can control Settings and upload new Org Data files

Any groups with less than 5 people is also automatically hidden to ensure privacy:

In this example, the company has less than 5 Senior Execs so their information is hidden by the system.

Sanjanaa_Ellur_0-1635272914511.png